Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
djcarpen11
Starting Member
25 Posts |
 Posted - 2010-06-17 : 05:02:04
|
| Hi,The company I work for has just upgraded from SQL 200o to 2008. So obviously moving forward we will be using SSIS instead of dta packages.If possible I'd like a couple of issuses I have clearing up. 1. Should we deploy the packages to msdb or a file system? I'm the DBA not the system admin so I can't set up file shares permissions etc...? 2.How do is set up a standard package template? To contain things like the package protection level and have a text box with the company standard acronyms for tasks? such as Execute SQL task must start SQL_XXXXX3.What is the best method for using configuration files going from Dev to Production servers? We currently don't have a QA processes in place. Thanks Dave |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-06-17 : 05:15:48
|
Maybe someone comes up here who has more experience but I have made some experiences by developing 2005-SSIS-Packages without schooling. It was a hard time "learning by doing" with all mistakes and consequences  Deploy to msdb because then the package is inside a backup if you do it on msdb.About template I can't tell you anything but maybe there is a way...Avoid Configuration Files if possible. The packages need them (in file system) every time they are running.Use the possibility to alter the connection managers in the jobsteps in SQL Server Agent instead.Avoid using SSIS Packages if it is possible to have a stored procedure for example that you can start directly in a SQL Server Agent job.
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
|
|
|
File System or MSDB?