dbTalk Databases Forums  

DTS Corruption if it was generated from a script

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss DTS Corruption if it was generated from a script in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Hugues Bellerive
 
Posts: n/a

Default DTS Corruption if it was generated from a script - 09-24-2004 , 02:53 PM






During the installation of our product, three things occur:
1- We install a version of embedded SQL Server;
2- We create our databases;
3- We generate a DTS package from a VbScript.

This later step is the problem: on VbScript-generated DTS packages, the
simple action of subsequently adding a new global variable will irrevocably
corrupt the DTS package. Removing the global variable won’t solve it. The DTS
package will no longer work properly. DTS packages created from script are
simply unchangeable.

However, on the development machine, if I follow the sequence of adding /
removing / editing global variables from the Enterprise GUI, every thing is
peachy.

Some one has any clue about how this is possible (or why it happens)?

Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: DTS Corruption if it was generated from a script - 09-25-2004 , 02:29 AM






What is the corruption i.e. what happens?
So you add a package that is from VBScript. You then add (how?) a GV to
that package?

I am asking these Qs so I can hope to repro.



--

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"Hugues Bellerive" <Hugues Bellerive (AT) discussions (DOT) microsoft.com> wrote in
message news:A2DC972C-4BE4-44E0-9AEC-1FC1C3C5E37F (AT) microsoft (DOT) com...
Quote:
During the installation of our product, three things occur:
1- We install a version of embedded SQL Server;
2- We create our databases;
3- We generate a DTS package from a VbScript.

This later step is the problem: on VbScript-generated DTS packages, the
simple action of subsequently adding a new global variable will
irrevocably
corrupt the DTS package. Removing the global variable won't solve it. The
DTS
package will no longer work properly. DTS packages created from script are
simply unchangeable.

However, on the development machine, if I follow the sequence of adding /
removing / editing global variables from the Enterprise GUI, every thing
is
peachy.

Some one has any clue about how this is possible (or why it happens)?



Reply With Quote
  #3  
Old   
Hugues Bellerive
 
Posts: n/a

Default Re: DTS Corruption if it was generated from a script - 09-27-2004 , 01:11 PM



(Actually, it's a VB application that dynamically creates the DTS packages.)

Once the installation is comlpeted, a customer asked for a modification, one
that required adding a GV. So, with Enterprise's GUI, I went in the DTS
section, openned the package, used the Package Properties GUI, and added my
new GV in tab GVs. I confirm it worked by selecting the new GV in the
variable list showed in VbScript editor (same as Disconnected Edit).

The impact is that global variable storage (mem) seams to be corrupted. As
an example, I have SQL queries that use GVs in a VbScript. When tracing the
script, I realized that my GVs were no longer accessible (using MsgBox showed
"Undisplayable").

Removing the newly added GV didn't put things back into place. GVs are from
this point corrupted.

Strange hey?

"Allan Mitchell" wrote:

Quote:
What is the corruption i.e. what happens?
So you add a package that is from VBScript. You then add (how?) a GV to
that package?

I am asking these Qs so I can hope to repro.

--

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Hugues Bellerive" <Hugues Bellerive (AT) discussions (DOT) microsoft.com> wrote in
message news:A2DC972C-4BE4-44E0-9AEC-1FC1C3C5E37F (AT) microsoft (DOT) com...
During the installation of our product, three things occur:
1- We install a version of embedded SQL Server;
2- We create our databases;
3- We generate a DTS package from a VbScript.

This later step is the problem: on VbScript-generated DTS packages, the
simple action of subsequently adding a new global variable will
irrevocably
corrupt the DTS package. Removing the global variable won't solve it. The
DTS
package will no longer work properly. DTS packages created from script are
simply unchangeable.

However, on the development machine, if I follow the sequence of adding /
removing / editing global variables from the Enterprise GUI, every thing
is
peachy.

Some one has any clue about how this is possible (or why it happens)?

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.