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 |
|
Rach2009
Starting Member
37 Posts |
 Posted - 2010-04-08 : 06:02:09
|
| Hi All,I have recently created (via the import wizard) a set of packages which I have saved to Integration Services-MSDB. I run the packages manually from here daily to import data. However, I have just discovered that other members of my team cannot see these saved packages on their version of SQL Server Management Studio. They can see the relevant database and tables here but not the packages. Any ideas why this is happening? I understand we are logged in as different users but can't see why they can see the databases the same as me, but not Integration Services? Will I need to re-create the packages from scratch on each PC? If so, is there some way of copying the packages from my area and saving them to other users Integration Services?I would very much appreciate anyones advice on this!Many ThanksRachel |
|
|
DBA in the making
Aged Yak Warrior
638 Posts |
Posted - 2010-04-08 : 06:32:27
|
| Are the packages stored in the msdb or filesystem? If they're in the msdb, then I think users must be members of the db_dtsoperator fixed server role of the msdb database in order to see them.There are 10 types of people in the world, those that understand binary, and those that don't. |
 |
|
|
|
|
|
SSIS Packages - Different Users