Events
Mar 31, 11 PM - Apr 2, 11 PM
The biggest SQL, Fabric and Power BI learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Applies to:
SQL Server
Replication supports on demand script execution for Subscribers to transactional and merge publications. This functionality copies the script to the replication working directory and then uses sqlcmd to apply the script at the Subscriber. By default, if there is a failure when applying the script for a subscription to a transactional publication, the Distribution Agent will stop. You can specify a Transact-SQL script to execute programmatically using replication stored procedures.
Compose and test the Transact-SQL script that will be executed on demand.
Save the script file to a location where it can be accessed by the Snapshot Agent for the publication.
At the Publisher on the publication database, execute sp_addscriptexec (Transact-SQL). Specify @publication
, the name of the script file with full UNC path created in step 2 for @scriptfile
, and one of the following values for @skiperror
:
0 - the agent will stop executing the script if an error is encountered.
1 - the agent will log errors and continue executing the script when errors are encountered.
The specified script will be executed at each Subscriber when the agent next runs to synchronize the subscription.
Events
Mar 31, 11 PM - Apr 2, 11 PM
The biggest SQL, Fabric and Power BI learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayTraining