Here's my situation. I have a need for a publisher database (read/write/update/ddl) in one location and a subscriber database in another. The database is small (about 50M), but it undergoes frequent changes to both data and table structures. Lag is not a huge issue (the data can be several hours off), but ease of use is. Is there a replication scheme in SQL Server 2000 that will allow the frequent changing of schema without too many extra steps? I visualize a snapshot setup that gets overwritten every couple hours. Does Snapshot Replication limit your ability to make schema changes like Transactional and Merge do?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Replication help
- Thread starter jtmarcot
- Start date
Similar threads
- Locked
- Question