January 5, 2006 at 6:58 am
SSIS has so many options for storing packages and configuration data. What is the BEST way? How are you storing, backing up and running your packages in production?
January 5, 2006 at 12:21 pm
Good question.
First of all I did not like the way SSIS defaulted to my documents.
So I created a directory on the SQL server call. You can change the folder defaults in studio.
C:\SQL2K5\SSIS\[Package groupings]
C:\SQL2K5\SSMS\[Query groupings]
That way through visual Studio you can just get to the documents in the same place. There are only two devlopers so I don't need to worry about securing who sees what. We see it all. Then we just have a backup run on that specific location every night and the packages get stored.
To upload them to the intergration server you need to use the manifest file. Not sure if you are familar with that yet. Then you can create a job on the in SSMS to execute the package on the intergration server. A bit daunting but it works logically for the most part.
January 6, 2006 at 1:37 am
On my current project we are still in the dev and test phase so we haven't thought about these things yet but I'll answer as best I can.
How are we running packages? This will be via SQL Server Agent
How are we backing up packages? We will be deploying packages to the file system so file system backups will be our method here
Storing configurations? We use inndirect configurations exclusively. They require an env variable (there's no anbiguity about where you store that) and an XML configuration file. Those configuration files are stored in a folder structure that also contains my packages and a few other things. Documented here: http://blogs.conchango.com/jamiethomson/archive/2006/01/05/2559.aspx
Hope that helps!
-Jamie
Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply