reading
You Should Read
archives
- September 2004
- October 2004
- November 2004
- December 2004
- January 2005
- April 2005
- May 2005
- June 2005
- July 2005
- August 2005
- September 2005
- October 2005
- November 2005
- December 2005
- January 2006
- February 2006
- March 2006
- April 2006
- May 2006
- June 2006
- July 2006
- August 2006
- September 2006
blogs I read
- Caspian Arts
- Coding Horror
- ComputerZen
- Joel On Software
- Knowing.net
- MSBuild Team Blog
- Rob Howard
- ScottGu
- Scott On Writting
- Signal vs. Noise
- SimpleBits Articles
Monday, September 25, 2006
SQL Server 2000 Replication Quirks
I am using Microsoft SQL Server 2000 Replication for one of my company's projects. I had never used replication, but it seemed like a good solution to the problem we were facing. The application has been running for about a month now and I am happy to say that I am pleased with Replication so far.
I released version 1.1 of the application this weekend and it included some minor database changes. I needed to add columns to existing tables, create two new tables, update existing stored procedures, and create new stored procedures to support the new tables. This would normally not be a big deal. Unfortunately replication makes adding columns to a replicated table a bit more complex.
Thankfully I found the following article to assist me with adding columns to existing tables that are being published via replication:
Altering Replicated Tables (SQL 2000)
Another oddity is that when I altered replicated stored procedures and updated the Snapshot, the changes to the stored procedure did not propagate to the subscribing database. After monitoring the subscriber for changes for over an hour, I manually updated the subscriber with the proc changes.
Content copyright ©2003-2006 Tod Birdsall
I released version 1.1 of the application this weekend and it included some minor database changes. I needed to add columns to existing tables, create two new tables, update existing stored procedures, and create new stored procedures to support the new tables. This would normally not be a big deal. Unfortunately replication makes adding columns to a replicated table a bit more complex.
Thankfully I found the following article to assist me with adding columns to existing tables that are being published via replication:
Altering Replicated Tables (SQL 2000)
Another oddity is that when I altered replicated stored procedures and updated the Snapshot, the changes to the stored procedure did not propagate to the subscribing database. After monitoring the subscriber for changes for over an hour, I manually updated the subscriber with the proc changes.