Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Ken Blum
Constraint Violating Yak Guru
383 Posts |
 Posted - 2003-01-20 : 13:51:36
|
| I currently have over 100 clients using the same single-user program with the same database structure in a Visual Foxpro database. I am going to change this to a SQL Server 2000 database so I may implement data replication back to a single Corporate SQL Server. This Corporate Server may then be queried to report on all clients separatley or combined.My main question is how I should setup the databases. Should I have separate databases for each client on the Corporate Server, or one single database on the corporate server and code each record in each table separately?1. If one single database, I imagine I would have to code each record in each table with a client code so a query could do..SELECT * FROM TABLE1 WHERE ClientCode = 1000 OR ClientCode = 2000If multiple databases then I would have to write it like...SELECT * FROM Database1000..TABLE1, Database2000..TABLE1and I may even have to use a UNION (yuckola)2. If one single corporate database, can I setup a replication to a client database that will only replicate data based on the clientcode for each record? Could this code be generated "on-the-fly" by the corporate server database during replication? What happens to UniqueID fields? 3. Also, is there a way to schedule replication to occur after a certain number of records have been added in the client database?Thanks in advance for the advice...Ken |
|
|
|
|
|
Database Design for use with Replication