Can these packages be altered in any one of the 3 locations?
Hopefully the changes would occur not to the locally deployed version of
the package rather the version you currently have booked into Source
Control which would be the same base version for all 3 servers. As for
keeping them in Sync so long as you make the changes in Source Control
then I would have a scheduled release cycle to all 3 environments at the
same time.
Sourcesafe and SSIS work well together. I have heard stories a while
back about large packages coming out mangled but I have not heard the
recently and certainly I have not expereinced it.
--
Allan Mitchell
http://wiki.sqlis.com |
http://www.sqlis.com |
http://www.sqldts.com |
http://www.konesans.com "imani_technology_spam@yahoo.com" <imani_technology_spam@yahoo.com>
[quoted text, click to view] wrote in message
news:1173765396.613431.240210@c51g2000cwc.googlegroups.com:
> I have a couple of questions about SSIS Best Practices. For example,
> what is the most efficient way to synchronize SSIS packages across 3
> servers? The package was originally identical in 3 different servers
> and I want to keep the changes identical. Also, how well does SSIS
> integrate with Visual Source Safe and what is the most efficient way
> to use them together?