|
Home > Archive > MS SQL Server DTS > January 2006 > Debugging VB Script within DTS Package
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Debugging VB Script within DTS Package
|
|
| Larry Bird 2006-01-21, 11:23 am |
| I’m experiencing a problem with a VB Script inside a DTS Package. When I
run the task via the Package designer it runs fine. However, when I run the
entire package the result is different.
I need to be able to debug the VB script within the package. The script
uses DTS global variables so I’m unable to run it as a standard script. The
server is a Windows 2003 Standard server running SQL server 2000 standard
edition.
Does anyone have any ideas?
Thanks
| |
| vadim.svinkin@gmail.com 2006-01-23, 11:24 am |
| I'm using combination of MsgBox and logging values to a couple of
tables through ADODB.Connection.
Vadim.
| |
| Darren Green 2006-01-23, 8:24 pm |
| Larry Bird wrote:
> I’m experiencing a problem with a VB Script inside a DTS Package. When I
> run the task via the Package designer it runs fine. However, when I run the
> entire package the result is different.
>
> I need to be able to debug the VB script within the package. The script
> uses DTS global variables so I’m unable to run it as a standard script. The
> server is a Windows 2003 Standard server running SQL server 2000 standard
> edition.
>
> Does anyone have any ideas?
>
> Thanks
>
You can use the MS Script Debugger, free download I believe.
Using a STOP statement should allow you to attach to the process. This
is not always 100% reliable, but a MsgBox will pause execution and you
can attach then.
Check the properties of the DTS node in EM, there is a JIT debug option
I think, probably need to turn it on. (It has been a while...)
--
Darren
http://www.sqldts.com
http://www.sqlis.com
|
|
|
|
|