Deploying an SSIS Package

Deploying an SSIS package

You can deploy a package to an instance of SQL server or to a file system.  The file deployment is the preferred choice of ycsoftware.

Obviously your first step is to copy the files located in the bin/deployment folder of your  (business intelligence studio) project  to a folder on the destination folder, then follow microsoft instructions below on deploying your package.

“To deploy packages to an instance of SQL Server

  1. Open the deployment folder on the target computer.
  2. Double-click the manifest file, <project name>.SSISDeploymentManifest, to start the Package Installation Wizard.
  3. On the Deploy SSIS Packages page, select the SQL Server deployment option.
  4. Optionally, select Validate packages after installation to validate packages after they are installed on the target server.
  5. On the Specify Target SQL Server page, specify the instance of SQL Server to install the packages to and select an authentication mode. If you select SQL Server Authentication, you must provide a user name and a password.
  6. On the Select Installation Folder page, specify the folder in the file system for the package dependencies that will be installed.
  7. If the package includes configurations, you can edit configurations by updating values in the Value list on the Configure Packages page.
  8. If you elected to validate packages after installation, view the validation results of the deployed packages.
To deploy packages to the file system
  1. Open the deployment folder on the target computer.
  2. Double-click the manifest file, <project name>.SSISDeploymentManifest, to start the Package Installation Wizard.
  3. On the Deploy SSIS Packages page, select the File system deployment option.
  4. Optionally, select Validate packages after installation to validate the packages after they are installed on the target server.
  5. On the Select Installation Folder page, specify the folder in which to install packages and package dependencies.
  6. If the package includes configurations, you can edit updatable configurations by updating values in the Value list on the Configure Packages page.
  7. If you elected to validate packages after installation, view the validation results of the deployed packages.”

Reference :

http://msdn.microsoft.com/en-us/library/ms140117.aspx

SQL Server Destination error “0x80040E14 “

Limitation of the SQL Server Destination Object

"If you attempt to use the SQL Server destination to bulk load data into a remote SQL Server database, you may see an error message similar to the following: "An OLE DB record is available. Source: "Microsoft SQL Server Native Client" Hresult: 0x80040E14 Description: "Could not bulk load because SSIS file mapping object 'Global\DTSQLIMPORT ' could not be opened. Operating system error code 2 (The system cannot find the file specified.)….

For loading data into SQL Server, you should consider using the SQL Server destination instead of the OLE DB destination.  ." 

 http://msdn.microsoft.com/en-us/library/ms141095.aspx