July 2, 2002 at 3:53 am
Hey,
I recently come accross a server that hosts a lot of DTS Jobs. A lot of these have single ActiveX Script Tasks inside them. From a brief look, these scripts, make connections (and lots of em!!) to an as400 as well as the local sql server itself! Basically rows are pulled from the as400 and filtered and rules are applied using VBScript and then inserted/updated to SQL connections. Not to mention that I also saw hardcoded connections including the sa password!! I was pretty shocked to say the least! I advised straight away to get rid of all the hardcoding and remove all traces of the sa password immediately.
However, I am curious about the approach of opening lots of ADO connections to the as400 and the local server. What kind of overhead could that incur? I've never used DTS in that way before?
Any thoughts on this?
Clive Strong
July 2, 2002 at 10:31 am
No more overhead than using the connections in DTS. Some people prefer to code them in ActiveX rather than the connection. They may get more flexibility. These are resources on the server, so you might want to run them from another box and point them to the correct SQL Server.
Steve Jones
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply