November 17, 2008 at 11:13 am
Hi, MSDN article
http://msdn.microsoft.com/en-us/library/ms151196.aspx
says that:
The following actions require the system to be quiesced. This means stopping activity on published tables at all nodes and making sure that each node has received all changes from all other nodes.
--Making schema changes
I just made a schema change in my test invironment, it went thru fine. May I know why is the case?
November 18, 2008 at 3:55 pm
KATHLEEN Y ZHANG (11/17/2008)
Hi, MSDN articlehttp://msdn.microsoft.com/en-us/library/ms151196.aspx
says that:
The following actions require the system to be quiesced. This means stopping activity on published tables at all nodes and making sure that each node has received all changes from all other nodes.
--Making schema changes
I just made a schema change in my test invironment, it went thru fine. May I know why is the case?
If you made the change on a live system you maybe "risking" loosing data. It does not mean that it cannot be done. In 2008 MS ensures that there is not data loss even if you don't do the "quiesce".
* Noel
November 19, 2008 at 7:34 am
Thanks Noel!
I know with sql 2005, it is the same for 'transactional replication with updatable subscription'. Do you know with sql 2008, does it allow schema change without loosing data for this type of replication as well?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply