Question on VB Scripting for SQL Server DTS

[Jaybee from his]

Hi all,

I'm going to be getting involved with the creation and reconfiguration of DTS jobs, however I've noticed that they'll require VB Script, which I'm not familiar with.

Without me reading an 1000pp book on learning all uses of VB Script, are there any articles/resources that focus exclusively or distinctly on the most common uses of vb script in databasing?

On a separate note, are there any ready-made sample applications I could download and connect to a SQL database for study purposes?

Thanks in advance,

JB.

[rmiao]

Check www.sqldts.com, there are some good stuffs.

[Jaybee from his]

Check www.sqldts.com, there are some good stuffs.

Just looked it up, no articles about VB Scripting for DTS.

Jaybee.

[MAK]

All activex scripts used in DTS package are vbscripts

[Jaybee from his]

All activex scripts used in DTS package are vbscripts

Apart from those written in Javascript.

Guys, what is this? I haven't found ANY info on this...are DBA's supposed to be damn developers now?

Seriously, this is getting frustrating...I've got an idiot Project Manager telling me,

"But I've heard DTS is easy"

Me: "Everything is easy when you know it."

Him: "This DTS thing is part of SQL Server, right?

Me: "Right".

Him: "And you're a SQL Server DBA, right?"

Me: "10 points".

Him: "So what's the problem?"

Me: "VB Script".

Him "But that's part of DTS, yes?"

Me: "It's used widely in DTS packages".

Him: "So, if DTS is a part of SQL Server, and you're a SQL Server DBA, why the hell don't you know how to VB Script?"

Me: "Because VB is learned by Developers, not DBA's"

Him: "So you're telling me we need an extra Developer?"

Me: "No. I'm telling you you need an extra Developer PLUS an extra DBA. I quit. Have a nice life."




Jaybee.

[MAK]

DBAs are not just Database Administrators anymore. (depends on the size of the shop.)

If you just support only the DBEngine container then whatever you said is 100% right. Even if you hire a developer when you are implementing it on the production environment you should know how to trouble shoot it.

Remember when you move to SQL Server 2005, developers can write CLR code and give it to you in the form of .dll file. you should know how to read and understand the code.

Alternate solution is you can create a standard say "We dont support CLR".

SQL Server is not just RDBMS. It is also has features like ETL, Reporting, Scheduler, notification, linked server, replication etc....

[MAK]

forgot.. it has also analysis service, full text search etc.