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 |
mayap
Starting Member
2 Posts |
Posted - 2007-11-14 : 11:08:20
|
Hi Experts,When you create a SSIS Project in Visual Studio and start adding many, many SSIS and several people do it, they are not being sorted when they get loaded into Visual Studio environment, unlike other objects such as web forms in ASP.NET or classes. as you can imagine, if you have about 100 of SSIS, it makes it very hard for anyone to find one SSIS to alter it.all these packages are being stored in some xml file, right? so, my boss wants me to write a tool that will open this file and order SSIS by names to make it easier for anyone in a team. i was wondering if anyone has done something like this already, or started. any leads, comments will be appreciated.thanks a bunch! |
|
Hommer
Aged Yak Warrior
808 Posts |
Posted - 2007-11-15 : 09:31:58
|
Two things I have seen in practice.One is to follow a naming convention well thought off ahead of time.Another is to use a master-children package to organize them in groups. |
 |
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2007-11-15 : 12:22:06
|
I don't add them to a project. Hold them as files - when you want to change one add it to an empty project then save it over the file.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
mayap
Starting Member
2 Posts |
Posted - 2007-11-15 : 15:08:02
|
OK, thanks Everyone for your help and tips, i really appreciate it. |
 |
|
|
|
|