November 11, 2001 at 12:00 am
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/bknight/savingpackages.asp
Brian Knight
Free SQL Server Training Webinars
November 12, 2001 at 8:46 am
In the article you state that you cannot view in the GUI a DTS package that was saved to VB. What I do is to comment out the Execute line that is generated by DTS when the package is saved and replace it with a Save line (using one of the various Save and SaveTo methods). Then I view that newly saved package in the GUI.
One Caveat: certain properties related to threading are explicitly set to make the package run in VB. To use the multi-threaded features of DTS, you will need to change those property values.
Russel Loski
Edited by - RLoski on 11/12/2001 08:46:51 AM
Russel Loski, MCSE Business Intelligence, Data Platform
November 12, 2001 at 10:39 am
Excellent idea. Thanks for sharing that.
Brian Knight
http://www.sqlservercentral.com/columnists/bknight
Brian Knight
Free SQL Server Training Webinars
January 23, 2002 at 8:44 am
Good article (I knew those old DTS versions were piling up there, but 1.2G?!? Yow!).
Brian mentioned having problems with 100M .DTS COM files bloating up with multiple versions. We avoided that problem by not using the GUI to generate the DTS files, but rather using the object model (and please pardon my weak terminology).
The short form is, you instantiate the DTS.Package object, use the .LoadFromSQLServer method (7 parameters in there), followed by the .SaveToStorageFile method... and voila, you have a .DTS file containing only the most recent version.
I wrote all this up as chunk of Foxpro code months ago, after reading obscure corners of BOL and much suffering; it works like a charm, and is integral to both our (external to SQL Server) source control and our deployment process.
Philip Kelley
January 23, 2002 at 12:02 pm
March 21, 2002 at 3:00 pm
Another advantage of the BAS file is that you can perform search and replace functions on it from your favorite text editor. This has come in handy for me when I have a half-dozen connections and need to change the server name.
BAS files also expose some of the task name properties in the DTS object model that can make the DTS output a lot mkore useful and eaier to debug.
The big caveat to BAS files, however, is that it completely botches any formatting you did in designer mode when you perform a save from VB (as mentioned by Philip Kelley).
Bryant E. Byrd, MCDBA
SQL Server DBA/Systems Engineer
Intellithought, Inc.
[font="Tahoma"]Bryant E. Byrd, BSSE MCDBA MCAD[/font]
Business Intelligence Administrator
MSBI Administration Blog
June 23, 2004 at 5:38 am
Another option is http://www.sqldts.com/default.aspx?242
Works great, and it can be done by an InstallScript, if you need to deploy to many servers.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply