Where to store SSIS packages?
-
I can store an SSIS package in the "Package Store", in the file system, or in msdb. Wonderful to have options but are there any guidlines\hints indicating when to use one over the other?
TIA,
barkingdog
-
Let me preface this by stating that I am not an IS expert. My packages are fairly simple.
I prefer the file system with the caveat that it is backed up daily. The "Package Store" is a default folder in the file system.
Storing a package in msdb means it will need to be exported to the file system in order to make changes and then imported again.
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
-
"I prefer the file system"
So do I. I was just puzzled by the numerous SSIS storage places. There must be some reason for all the options, I reasoned.
Barkingdog
-
I'm sure someone at M$ knows why
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
-
One on the biggest reasons to store the packages in the msdb database is you can leverage the new security roles. The roles grant security access to packages, without elevating privileges. The roles are db_dtsadmin, db_dtsltuser, db_dtsoperator.
More info:
-
I agree with Adam. I also suspect that, because a lot of people were used to storing DTS packages in msdb in SQL 2000, MS kept that option.
Greg
-
We have our project on the server file system, but run our packages from MSDB.
File system has it's own backup, and so does SQL server.
This also allows different access levels to be applied ( i.e. some can open and modify the project, while some can only run the package from msdb ).
Be sure to look at package security in Books On Line. Especially pay attention to the defaults if you have multiple developers.
Greg E
-
I recommend you to go through this link
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply