You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> You have the option of editing the T-SQL to add a leading `#` to the table names, which creates them as temporary tables in *tempdb*. This is useful for demonstration purposes, when no test database is available. Any reference to foreign keys are not enforced during their use and temporary tables are deleted automatically when the connection closes after the program finishes running.
30
+
> You have the option of editing the T-SQL to add a leading `#` to the table names, which creates them as temporary tables in *tempdb*. This is useful for demonstration purposes, when no test database is available. Foreign key references aren't enforced during their use, and temporary tables are deleted automatically when the connection closes after the program finishes running.
31
31
32
32
### To compile and run
33
33
@@ -46,7 +46,7 @@ The C# program is logically one .cs file, and is physically divided into several
46
46
-*cb.Password*
47
47
-*cb.InitialCatalog*
48
48
49
-
1.Verify the assembly *System.Data.dll* is referenced. To verify, expand the **References** node in the **Solution Explorer** pane.
49
+
1.Add the **Microsoft.Data.SqlClient** NuGet package to your project. In Visual Studio, right-click on the project in **Solution Explorer**, select **Manage NuGet Packages**, and search for `Microsoft.Data.SqlClient`.
50
50
51
51
1. To build and run the program from Visual Studio, select the **Start** button. The report output is displayed in a program window, though GUID values will vary between test runs.
52
52
@@ -82,7 +82,7 @@ The C# program is logically one .cs file, and is physically divided into several
Copy file name to clipboardExpand all lines: docs/integration-services/ssis-quickstart-deploy-dotnet.md
+27-27Lines changed: 27 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Deploy an SSIS project with .NET code (C#)"
3
3
description: "Deploy an SSIS project with C# code in a .NET app"
4
4
author: chugugrace
5
5
ms.author: chugu
6
-
ms.date: "05/21/2018"
6
+
ms.date: 02/09/2026
7
7
ms.service: sql
8
8
ms.subservice: integration-services
9
9
ms.topic: quickstart
@@ -34,17 +34,17 @@ You can use the information in this quickstart to deploy an SSIS project to the
34
34
35
35
- Azure SQL Database. For more info about deploying and running packages in Azure, see [Lift and shift SQL Server Integration Services workloads to the cloud](lift-shift/ssis-azure-lift-shift-ssis-packages-overview.md).
36
36
37
-
You cannot use the information in this quickstart to deploy an SSIS package to SQL Server on Linux. For more info about running packages on Linux, see [Extract, transform, and load data on Linux with SSIS](../linux/sql-server-linux-migrate-ssis.md).
37
+
You can't use the information in this quickstart to deploy an SSIS package to SQL Server on Linux. For more info about running packages on Linux, see [Extract, transform, and load data on Linux with SSIS](../linux/sql-server-linux-migrate-ssis.md).
38
38
39
39
## For Azure SQL Database, get the connection info
40
40
41
41
To deploy the project to Azure SQL Database, get the connection information you need to connect to the SSIS Catalog database (SSISDB). You need the fully qualified server name and login information in the procedures that follow.
42
42
43
-
1.Log in to the [Azure portal](https://portal.azure.com/).
44
-
2. Select **SQL Databases** from the left-hand menu, and then select the SSISDB database on the **SQL databases** page.
45
-
3. On the **Overview** page for your database, review the fully qualified server name. To see the **Click to copy** option, hover over the server name.
43
+
1.Sign in to the [Azure portal](https://portal.azure.com/).
44
+
2. Select **SQL Databases** from the left-hand menu, and then select the SSISDB database on the **SQL databases** page.
45
+
3. On the **Overview** page for your database, review the fully qualified server name. To see the **Click to copy** option, hover over the server name.
46
46
4. If you forget your Azure SQL Database server login information, navigate to the SQL Database server page to view the server admin name. You can reset the password if necessary.
47
-
5.Click**Show database connection strings**.
47
+
5.Select**Show database connection strings**.
48
48
6. Review the complete **ADO.NET** connection string. Optionally, your code can use a `SqlConnectionStringBuilder` to recreate this connection string with the individual parameter values that you provide.
49
49
50
50
## Supported authentication method
@@ -53,23 +53,24 @@ Refer to [authentication methods for deployment](ssis-quickstart-deploy-ssms.md#
53
53
54
54
## Create a new Visual Studio project
55
55
56
-
1. In Visual Studio, choose **File**, **New**, **Project**.
56
+
1. In Visual Studio, choose **File**, **New**, **Project**.
57
57
2. In the **New Project** dialog, and expand **Visual C#**.
58
58
3. Select **Console App** and enter *deploy_ssis_project* for the project name.
59
-
4.Click**OK** to create and open the new project in Visual Studio.
59
+
4.Select**OK** to create and open the new project in Visual Studio.
60
60
61
61
## Add references
62
62
1. In Solution Explorer, right-click the **References** folder and select **Add Reference**. The **Reference Manager** dialog box opens.
63
63
2. In the **Reference Manager** dialog box, expand **Assemblies** and select **Extensions**.
64
64
3. Select the following two references to add:
65
65
- Microsoft.SqlServer.Management.Sdk.Sfc
66
66
- Microsoft.SqlServer.Smo
67
-
4.Click the **Browse** button to add a reference to **Microsoft.SqlServer.Management.IntegrationServices**. (This assembly is installed only in the global assembly cache (GAC).) The **Select the files to reference** dialog box opens.
67
+
4.Select the **Browse** button to add a reference to **Microsoft.SqlServer.Management.IntegrationServices**. (This assembly is installed only in the global assembly cache (GAC).) The **Select the files to reference** dialog box opens.
68
68
5. In the **Select the files to reference** dialog box, navigate to the GAC folder that contains the assembly. Typically this folder is `C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.Management.IntegrationServices\14.0.0.0__89845dcd8080cc91`.
69
-
6. Select the assembly (that is, the .dll file) in the folder and click **Add**.
70
-
7. Click **OK** to close the **Reference Manager** dialog box and add the three references. To make sure the references are there, check the **References** list in Solution Explorer.
69
+
6. Select the assembly (that is, the .dll file) in the folder and select **Add**.
70
+
7. Select **OK** to close the **Reference Manager** dialog box and add the three references. To make sure the references are there, check the **References** list in Solution Explorer.
71
+
8. Add the **Microsoft.Data.SqlClient** NuGet package. Right-click on the project in **Solution Explorer**, select **Manage NuGet Packages**, search for `Microsoft.Data.SqlClient`, and install it.
71
72
72
-
## Add the C# code
73
+
## Add the C# code
73
74
1. Open **Program.cs**.
74
75
75
76
2. Replace the contents of **Program.cs** with the following code. Add the appropriate values for your server, database, user, and password.
@@ -80,7 +81,7 @@ Refer to [authentication methods for deployment](ssis-quickstart-deploy-ssms.md#
Copy file name to clipboardExpand all lines: docs/integration-services/ssis-quickstart-deploy-powershell.md
+23-22Lines changed: 23 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Deploy an SSIS project with PowerShell"
3
3
description: "Deploy an SSIS project with PowerShell"
4
4
author: chugugrace
5
5
ms.author: chugu
6
-
ms.date: "05/21/2018"
6
+
ms.date: 02/09/2026
7
7
ms.service: sql
8
8
ms.subservice: integration-services
9
9
ms.topic: quickstart
@@ -30,17 +30,17 @@ You can use the information in this quickstart to deploy an SSIS project to the
30
30
31
31
- Azure SQL Database. For more info about deploying and running packages in Azure, see [Lift and shift SQL Server Integration Services workloads to the cloud](lift-shift/ssis-azure-lift-shift-ssis-packages-overview.md).
32
32
33
-
You cannot use the information in this quickstart to deploy an SSIS package to SQL Server on Linux. For more info about running packages on Linux, see [Extract, transform, and load data on Linux with SSIS](../linux/sql-server-linux-migrate-ssis.md).
33
+
You can't use the information in this quickstart to deploy an SSIS package to SQL Server on Linux. For more info about running packages on Linux, see [Extract, transform, and load data on Linux with SSIS](../linux/sql-server-linux-migrate-ssis.md).
34
34
35
35
## For Azure SQL Database, get the connection info
36
36
37
37
To deploy the project to Azure SQL Database, get the connection information you need to connect to the SSIS Catalog database (SSISDB). You need the fully qualified server name and login information in the procedures that follow.
38
38
39
39
1. Sign in to the [Azure portal](https://portal.azure.com/).
40
-
2. Select **SQL Databases** from the left-hand menu, and then select the SSISDB database on the **SQL databases** page.
41
-
3. On the **Overview** page for your database, review the fully qualified server name. To see the **Click to copy** option, hover over the server name.
40
+
2. Select **SQL Databases** from the left-hand menu, and then select the SSISDB database on the **SQL databases** page.
41
+
3. On the **Overview** page for your database, review the fully qualified server name. To see the **Click to copy** option, hover over the server name.
42
42
4. If you forget your Azure SQL Database server login information, navigate to the SQL Database server page to view the server admin name. You can reset the password if necessary.
43
-
5.Click**Show database connection strings**.
43
+
5.Select**Show database connection strings**.
44
44
6. Review the complete **ADO.NET** connection string.
dir "$($catalog.PSPath)\Folders\$TargetFolderName\Projects\$ProjectName\Packages" |
76
+
dir "$($catalog.PSPath)\Folders\$TargetFolderName\Projects\$ProjectName\Packages" |
77
77
SELECT Name, DisplayName, PackageId
78
78
```
79
79
80
80
## PowerShell script
81
81
Provide appropriate values for the variables at the top of the following script, and then run the script to deploy the SSIS project.
82
82
83
83
> [!NOTE]
84
+
> The following script requires the **Microsoft.Data.SqlClient** assembly. Install it from the [NuGet package](https://www.nuget.org/packages/Microsoft.Data.SqlClient) and ensure the DLL is accessible to PowerShell. You can load it with `Add-Type -Path "path\to\Microsoft.Data.SqlClient.dll"` before running the script.
85
+
>
84
86
> The following example uses Windows Authentication to deploy to a SQL Server on premises. To use SQL Server authentication, replace the `Integrated Security=SSPI;` argument with `User ID=<user name>;Password=<password>;`. If you're connecting to an Azure SQL Database server, you can't use Windows authentication.
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments