Groups | Blog | Home
all groups > sql server data warehouse > april 2004 >

sql server data warehouse : VB 6 ADO vs Microsoft Query Analyzer



Maurice Boers
4/26/2004 3:51:02 PM
Hello

I have a sql update statement thats quite large with several "select nests".
It generally takes an hour to run when I need to effect a lot of records.

In VB6 using ADO, I issue the statement and sometimes the update doesn't
actually preform the write (I think when I get over a certain # of records
being updated). whereas the same statement (printed my string & copy/pasted
in Microsoft Query Analyzer) functions just fine.

Can anyone give me a hint on what ado setting may make VB preform like query
analyzer

(I could put my nests in temp tables, but I'm curoius what the difference in
defaults are between the 2)

Thanks
Maurice


Val Mazur
4/26/2004 11:55:36 PM
Hi,

You should be more specific. Do you get any error? If yes, then what kind
of. If this is not an error, then you should describe what is wrong

--
Val Mazur
Microsoft MVP


[quoted text, click to view]

Greg Linwood
4/27/2004 9:25:40 AM
Is your VB6 app receiving an error when it doesn't perform the write? Is the
app checking for errors & notifying you? Sometimes this is simply because
the VB6 / ADO timeout setting is made too low at the connection, or command
level causing the query to "timeout"..

Regards,
Greg Linwood
SQL Server MVP

[quoted text, click to view]

Kevin Frey
5/3/2004 10:18:42 AM
My best guess on the information supplied is that the timeout figure for the
ADO Connection is set too low. For large batch operations like these I would
disable the timeout altogether.

Kevin.

[quoted text, click to view]

AddThis Social Bookmark Button