Comments on: Running a SQL stored procedure with an ADO Command

By: Eletric Bikes

Eletric Bikes — Thu, 13 Nov 2008 14:09:40 +0000

Cool - stored procedures take a lot of overhead from the server. Nice also to see someone using ASP VbScript.

By: What Makes Fashion

What Makes Fashion — Wed, 12 Nov 2008 11:23:55 +0000

Very useful tips. Most people are completely unaware how their scripts impact the server.

By: IIS Web Hosting

IIS Web Hosting — Sat, 23 Aug 2008 01:35:11 +0000

Very useful article for those wanting to economise on server resources. Web developers need to know more about what is going on when their scripts call the server. Knowing this will make them think economically (stored procedures, caching etc).

By: MKTapps

MKTapps — Mon, 04 Aug 2008 18:03:22 +0000

Nicely illustrated.

You should use the ADO constants from Microsoft instead of just the numbers. They can be found by searching for ADOVBS.INC .

By: YAZILIM

YAZILIM — Wed, 09 Jul 2008 18:51:34 +0000

oh it’s very useful information.Thanks a lot

By: ADODB.Command vbscript datatypes - Eniro

ADODB.Command vbscript datatypes - Eniro — Tue, 29 Apr 2008 12:45:46 +0000

[…] Running a SQL stored procedure with an ADO Command | TechnowledgeBase […]

By: Alyssa

Alyssa — Thu, 24 Apr 2008 07:53:42 +0000

it sounds so advance for me..

it confused me…

want to learn more of it..

By: estetik

estetik — Tue, 01 Apr 2008 09:37:42 +0000

Very useful information for me here.

By: W-Files » Blog Archive » procedury składowane z vbs

W-Files » Blog Archive » procedury składowane z vbs — Tue, 11 Mar 2008 11:54:50 +0000

[…] pamięci - bardzo przydatny link Dodaj […]

By: Gabriel

Gabriel — Thu, 06 Mar 2008 13:58:44 +0000

TY for the script, it works fine.
Maybe you should consider adding the following sentence, to avoid timeout problems when the SP takes a long time to complete:

after:
set cnCmd=CreateObject(”ADODB.Command”)

add:
cnCmd.CommandTimeout = 0