sql server - Shared Data Sources vs. OLE DB Connections In SSIS -
i've been using shared data sources in of ssis projects because thought "best practice". however, under source control (tfs) every time open package updates data source connection in package. either have roll change or check in nonsense description.
i saw ssis best practice blog entry , got me thinking whether shared data sources way go.
don’t use data sources: no, don't mean data source components. mean .ds files can add ssis projects in visual studio in "data sources" node there in every ssis project create. remember data sources not feature of ssis - feature of visual studio, , significant difference. instead, use package configurations store connection string connection managers in packages. best road forward smooth deployment story, whereas using data sources dead-end road. nowhere.
what experiences data sources, configuration , source control?
we use svn, doesn't integrate in same way tfs does. when starting out ssis, used shared datasource, got me sorts of trouble when uploaded package run on schedule. use xml configuration files (package configurations) provide connection properties, , i've never had trouble these.
so agree, share datasources = bad idea/lack of hair
Comments
Post a Comment