hosting SSIS packages where?

After i create a SSIS package, where can i put it or store it in the SQL SERVER 2005 so that i can execute it later on?

You can execute dtsx file directly or use dtexec command

It's better using Agent Job,and define schedule

|||

You could stored (I'm not wrong) it in three different places:

In the SSIS File System

In MSDB

In FAT/NTFS

You can execute a SSIS from a job, .net framework 2.0 code, VbScript, with DTEXECUI, etc..

|||Hi,

The option to do this is available once you have built you're project and you have done this whilst the CreateDeploymentUtility is True. All you then have to do is go to the deployment folder (usually in the bin directory) and run the .SSISDeploymentManifest file. This will give you all deployment options including where to store your package.

This link gves some info on how to execute the packages programmatically:

http://msdn2.microsoft.com/en-us/library/ms403355.aspx

Hope this is of use to you.

Cheers,

Grant|||

Grant Swan wrote:

Hi,

The option to do this is available once you have built you're project and you have done this whilst the CreateDeploymentUtility is True. All you then have to do is go to the deployment folder (usually in the bin directory) and run the .SSISDeploymentManifest file. This will give you all deployment options including where to store your package.

This link gves some info on how to execute the packages programmatically:

http://msdn2.microsoft.com/en-us/library/ms403355.aspx

Hope this is of use to you.

Cheers,

Grant

I don't understand what you just said... You can just upload a package to SQL Server (MSDB, SSIS File System, etc...) and execute it there via a number of methods. Some of those methods require that you have Integration Services installed on your local computer.|||He informing the poster that he can use the deployment utility to deploy his packages, and it will show him the different options available.|||

As I'm still coming up to speed on SSIS and have only worked with it for a couple of months, I can only speak of my own first hand experience. Others may take other approaches that are easier/better/simpler, etc.

First, I find that developing SSIS packages in the Business Intelligence/Visual Studio environment seems to work better when using the Visual Studio project/solution approach with the packages stored on a local development machine's hard disk. During this develop/test period I usually select the option to encrypt the package(s) with user credentials.

Then, when I've completed my development and testing and I'm ready to run the packages from SQL Server Agent for instance, I use the Save Copy As functionality to save the individual .dtsx packages to SQL Server. This Save Copy As functionality gets a little tricky to find as the option is only available when the package is open and a designer is actively selected. I do this mainly to remove dependencies on a particular user's credentials or a particular password, etc. from the security mix that is involved in getting these packages to run correctly from SQL Server Agent, etc. While I am using the Save Copy As functionality, to save it to SQL Server rather than the file system, one of the options presented is to change the security model for the package from encrypt with user credentials to that of letting SQL Server manage the security thru roles and permissions functionality inherent is SQL Server.

This works well for me in a design,program, test, deploy environment as it lets me make clear delineations between packages at the various stages, etc.

Hope this helps.

Steve Wells

|||

I got an error

"An OLE DB error 0x80004005 (unable to complete login process due to delay in opening server connection) occurred while enumerating packages. A SQL statement was issued and failed."

The below is my config:

Package location : SQL server

Server : Computer Name

USERNAME: < sql server login >

PASSWORD: <sql server pass>

package path: <I cannot select!! I got the above error>