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.

All Forums  SQL Server 2008 Forums  SQL Server Administration (2008)  Change Tracking and Log Shipping

Author  Topic  TimHW Starting Member 1 Post Posted - 2009-11-19 : 19:54:57 I have a set up with 2 servers that need to continuously share data but that aren't continuously connected. To achieve this, I use Log Shipping to ship changes from the remote server to a staging database on the local server. This works well since the logs are transmitted when the link is up and just stored when it's not. Change Tracking is enabled on all databases. I then extract the changed data from the staging database into my live database. I've been using Change Tracking to locate the newly changed data and that seems to work well on its own too. My problem comes when I try and refer to the Change Tracking function changetable(), in the staging database. Although all the newly changed data has been successfully shipped and is available in the database, the changetable() function is not showing it. It's only if I take the staging database out of stabdby mode that the changetable() function shows the new changes, but of course this means the Log Shipping can't carry on which it needs to as this is supposed to be continuous. Has anybody else tried using Change Tracking on a Log Shipping secondary database? If so, how did you get it to work? Any help would be much appreciated. Thanks, Tim