如何不借助SSDT的Deploy选项部署SQL Server 2012的SSIS项目

Hi there! Let's walk through exactly how you can package your SSIS project for your client to deploy on their SQL Server 2012 instance—no SSDT required on their end. Here's what you need to prepare, plus the step-by-step methods they can use:

Step 1: Prepare the Deployment Package from Your SSDT Environment #

First, you'll need to export your project into a portable deployment file that your client can use:

• In SSDT, right-click your SSIS project in the Solution Explorer.
• Select Export Deployment Utility.
• Follow the wizard prompts—this will generate an .ispac file (usually in your project's bin\Deployment folder). This file is a compressed package containing all your SSIS packages, parameters, project configurations, and dependencies.
• If you have external configuration files (.dtsconfig), include those as well so your client can apply environment-specific settings.

Step 2: Client Deployment Methods (No SSDT Needed) #

Your client can use any of these built-in tools that come with SQL Server 2012 Integration Services (SSIS) — they don't need to install SSDT.

Method 1: Use the Integration Services Deployment Wizard (Graphical Interface) #

This is the most user-friendly option for clients who prefer a GUI:

1. On their server, navigate to the SSIS Binn folder (default path: C:\Program Files\Microsoft SQL Server\110\DTS\Binn — note that 110 corresponds to SQL Server 2012).
2. Run ISDeploymentWizard.exe.
3. Select Deploy project and click Next.
4. Choose Project deployment file, then browse to the .ispac file you provided. Click Next.
5. Enter their target SQL Server instance name, then select or create a target project folder (where the SSIS project will live on their server). Click Next.
6. Review the deployment summary, then click Deploy to finish.

Method 2: Use dtutil.exe (Command Line) #

Great for automation or clients comfortable with command-line tools:

• Open Command Prompt as an administrator on their server.
• Run a command like this (replace placeholders with their actual paths/server name):

  dtutil.exe /FILE "C:\Path\To\Your\Project.ispac" /SQL "\TargetProjectFolder\YourProjectName" /SERVER "TheirSQLInstanceName"
  

  • /FILE: Path to your .ispac file
  • /SQL: The full path to where the project should be stored on their SSIS server (include the folder and project name)
  • /SERVER: Their target SQL Server instance name

Method 3: Import via SQL Server Management Studio (SSMS) #

If your client has SSMS installed (2012 or newer), they can use this graphical approach:

1. Open SSMS and connect to their target server's Integration Services service.
2. Expand the Projects folder (under the Integration Services node), right-click and select Import Project....
3. Choose Project deployment file, browse to your .ispac file, then enter the desired project name and target folder.
4. Follow the remaining prompts to complete the import.

Key Notes for Your Client #

• Ensure their server has SQL Server 2012 Integration Services (SSIS) installed — without this, none of the above tools will be available.
• If your project uses custom SSIS components or third-party drivers (like ODBC connectors for specific databases), make sure they install those on their server before deploying.
• If you provided .dtsconfig files, they can apply these post-deployment via SSMS (right-click the project → Configure) or using dtutil.exe commands.
• The user deploying the project needs appropriate permissions on the target SSIS server (e.g., membership in the ssis_admin role, or permissions to create/modify SSIS projects).

内容的提问来源于stack exchange，提问作者Agustin Zanini