Application.SaveToSqlServerAs Method

Article
12/15/2008

Saves a package to an instance of SQL Server with a new name.

Espace de noms: Microsoft.SqlServer.Dts.Runtime
Assembly: Microsoft.SqlServer.ManagedDTS (in microsoft.sqlserver.manageddts.dll)

Syntaxe

'Déclaration
Public Sub SaveToSqlServerAs ( _
    package As Package, _
    events As IDTSEvents, _
    packagePath As String, _
    serverName As String, _
    serverUserName As String, _
    serverPassword As String _
)

public void SaveToSqlServerAs (
    Package package,
    IDTSEvents events,
    string packagePath,
    string serverName,
    string serverUserName,
    string serverPassword
)

public:
void SaveToSqlServerAs (
    Package^ package, 
    IDTSEvents^ events, 
    String^ packagePath, 
    String^ serverName, 
    String^ serverUserName, 
    String^ serverPassword
)

public void SaveToSqlServerAs (
    Package package, 
    IDTSEvents events, 
    String packagePath, 
    String serverName, 
    String serverUserName, 
    String serverPassword
)

public function SaveToSqlServerAs (
    package : Package, 
    events : IDTSEvents, 
    packagePath : String, 
    serverName : String, 
    serverUserName : String, 
    serverPassword : String
)

Paramètres

package
The package to save.

events
The IDTSEvents object.

packagePath
The path and new name to assign to the package. The parameter packagePath is in the format of \\folder\\packageName. If packagePath is specified without an existing folder, the package will be saved with this parameter as its new name.

serverName
The name of the instance of SQL Server.

serverUserName
The name of the account used to log on to the instance of SQL Server.

serverPassword
The password of the user account.

Exemple

The following code example saves the sample package named ExecuteProcess.dtsx to the msdb folder, with a new name of myNewPackage. To verify that the package was saved, run the following Transact-SQL query against the msdb database. The query returns all packages stored in the msdb system table.

select * from sysdtspackages90

Or, connect to the Integration Services service, expand Stored Packages, and then expand MSDB. The package with the name specified in packagePath will be listed.

static void Main(string[] args)
        {
           // The variable pkg points to the location
           // of the ExecuteProcess package sample 
           // that is installed with the SSIS samples.
            string pkg = @"C:\Program Files\Microsoft SQL Server\90\Samples\Integration Services\Package Samples\ExecuteProcess Sample\ExecuteProcess\UsingExecuteProcess.dtsx";
            
            Application app = new Application();
            Package p = app.LoadPackage(pkg, null);

           // Save the package to the SQL Server msdb folder, which is
           // also the MSDB folder in the Integration Services service, or as a row in the
           //sysdtspackags90 table.
            app.SaveToSqlServerAs(p, null, "myNewPackage", "yourserver", null, null);
        }

Shared  Sub Main(ByVal args() As String)
           ' The variable pkg points to the location
           ' of the ExecuteProcess package sample 
           ' that is installed with the SSIS samples.
            Dim pkg As String =  "C:\Program Files\Microsoft SQL Server\90\Samples\Integration Services\Package Samples\ExecuteProcess Sample\ExecuteProcess\UsingExecuteProcess.dtsx" 
 
            Dim app As Application =  New Application() 
            Dim p As Package =  app.LoadPackage(pkg,Nothing) 
 
           ' Save the package to the SQL Server msdb folder, which is
           ' also the MSDB folder in the Integration Services service, or as a row in the
           'sysdtspackags90 table.
            app.SaveToSqlServerAs(p, Nothing, "myNewPackage", "yourserver", Nothing, Nothing)
End Sub

Sécurité des threads

Any public static (Shared in Microsoft Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Plateformes

Plateformes de développement

Pour obtenir la liste des plateformes prises en charge, consultez Configuration matérielle et logicielle requise pour l'installation de SQL Server 2005.

Plateformes cibles

Pour obtenir la liste des plateformes prises en charge, consultez Configuration matérielle et logicielle requise pour l'installation de SQL Server 2005.

Voir aussi

Référence

Application Class
Application Members
Microsoft.SqlServer.Dts.Runtime Namespace

Partager via