{"id":873,"date":"2015-01-10T20:54:47","date_gmt":"2015-01-10T14:54:47","guid":{"rendered":"http:\/\/dotnetsql.info\/net-sql\/?p=873"},"modified":"2015-07-09T16:08:33","modified_gmt":"2015-07-09T10:08:33","slug":"how-to-change-default-snapshot-folder-for-replication","status":"publish","type":"post","link":"http:\/\/dotnetsql.info\/net-sql\/index.php\/how-to-change-default-snapshot-folder-for-replication\/","title":{"rendered":"How to change default snapshot folder for Replication?"},"content":{"rendered":"

Scenario<\/strong><\/h3>\n

You’ve set up replication initially by using the GUI and accepting all defaults and now due to growth you need to change your default replication snapshot folder location to another drive since the current location is a local disk and cannot be expanded to accommodate the growth.<\/p>\n

This concerns you as you cannot afford downtime to perform a re-initialization of all your existing subscribers as they are needed to run the business.<\/p>\n

Solution<\/strong><\/p>\n

You can change the snapshot location without having to perform a re-initialization. The only caveat to this is you do need to generate a new snapshot. This snapshot will not be applied to your subscribers, but has to go through the generation process. I recommend doing this at night or weekends to minimize the impact of the snapshot agent locking tables and contention on the publisher database.<\/p>\n

Current Snapshot Location for a Publication<\/strong><\/h3>\n

You can see the snapshot folder is currently pointed at a share called “\Some_Server_Name\\Share”. This is your snapshot location that will change later in the tip.\u00a0 To get to this screen right click on your publication and select Properties and click on Snapshot.\u00a0 You could change the location of the snapshot here, but this would need to be done for all publications.<\/p>\n

Current Snapshot Filesystem Folder<\/strong><\/h3>\n

This shows the snapshot files that are located in “\Some_Server_Name\\Share” meaning it was used to perform the initialization of this subscription.<\/p>\n

Changing Default Snapshot Location<\/strong><\/h3>\n

The script below changes the default snapshot location to “\Some_Server_Name\\Share2” from “\Some_Server_Name\\Share” for all publications..<\/p>\n

In your environment this could be a different mount point that has expandable storage. This is accomplished by calling sp_changedistpublisher<\/strong> and updating the working directory. This procedure takes a “publisher”, “property” and “value” parameters and needs to be run on the distributor<\/strong>.\u00a0 You can learn more about this here sp_changedistpublisher<\/a>.<\/p>\n

USE distribution<\/pre>\n
exec sp_changedistpublisher<\/pre>\n
\u00a0\u00a0\u00a0\u00a0@publisher = 'Some_Server_Name',<\/pre>\n
\u00a0\u00a0\u00a0\u00a0@property = 'working_directory',<\/pre>\n
\u00a0\u00a0\u00a0\u00a0@value = '\\\\Some_Server_Name\\Share2'<\/pre>\n
This can also be changed from SSMS by right clicking on Replication, selecting Properties, select Publishers and click on “…” to bring up this window.<\/p>\n
Synchronization After Changing Snapshot Location<\/strong><\/h3>\n
As you can see the sync completed without error after changing the snapshot location. I inserted some rows after changing the snapshot location and performed a sync manually to ensure there were no errors in replication.<\/p>\n
New Snapshot Location<\/strong><\/h3>\n
When looking at the publication properties a second time, you can see it is now showing “\Some_Server_Name\\Share2” instead of the original snapshot location of “\Some_Server_Name\\Share”.<\/p>\n
<\/h3>\n
As you can see changing the snapshot location was a painless process and the next time the snapshot agent runs it will write to the new location. Normal synchronization occurs without interruption.<\/p>\n
Thanks for reading this article,<\/strong><\/p>\n
Next steps :<\/strong><\/p>\n
    \n
  1. Share this with your colleagues because Sharingis Learning<\/strong><\/li>\n
  2. Comment below if you need any assistance<\/strong><\/li>\n<\/ol>\n
    Powered by CodeReview – Let’s make it Better!<\/a><\/strong><\/em><\/p>\n
    Share this:<\/h3>