Publication.ReplicateUserDefinedScript-Methode
Replicates the execution of a user-defined script to the Subscribers of a specified publication.
Namespace: Microsoft.SqlServer.Replication
Assembly: Microsoft.SqlServer.Rmo (in Microsoft.SqlServer.Rmo.dll)
Syntax
'Declaration
Public Sub ReplicateUserDefinedScript ( _
scriptFilePath As String _
)
'Usage
Dim instance As Publication
Dim scriptFilePath As String
instance.ReplicateUserDefinedScript(scriptFilePath)
public void ReplicateUserDefinedScript(
string scriptFilePath
)
public:
void ReplicateUserDefinedScript(
String^ scriptFilePath
)
member ReplicateUserDefinedScript :
scriptFilePath:string -> unit
public function ReplicateUserDefinedScript(
scriptFilePath : String
)
Parameter
- scriptFilePath
Typ: System.String
A String value that specifies the file name and full path to the Transact-SQL script file.
Ausnahmen
| Ausnahme | Bedingung |
|---|---|
| ApplicationException | The server is not running SQL Server 2000 or later. |
| ArgumentException | The passed String value is nullein NULL-Verweis (Nothing in Visual Basic), empty, or too long, or the path is not a valid path. |
Hinweise
The ReplicateUserDefinedScript method is only supported for transactional and merge publications.
The script is copied to the Distributor when ReplicateUserDefinedScript is first invoked. The Distribution Agent or the Merge Agent then applies the copy at the Distributor to the Subscriber. Any modifications to the script after ReplicateUserDefinedScript will not be replicated. You will need to call this method again.
Using the ReplicateUserDefinedScript method to post a script file for publications using File Transfer Protocol (FTP) for snapshot delivery is only supported for SQL Server Subscribers.
The ReplicateUserDefinedScript method can only be called by members of the sysadmin fixed server role at the Publisher or by members of the db_owner fixed database role on the publication database.
Calling ReplicateUserDefinedScript is equivalent to executing the sp_addscriptexec (Transact-SQL) stored procedure.