Welcome! Log In Create A New Profile

Advanced

SQL server native driver

Posted by Arie 
Forum List Message List New Topic
Arie
SQL server native driver
May 29, 2008 12:13PM
Hi,
currently my application uses oledb to connect to a MSSQL-server. Works fine, but not very fast.
I noticed that using HExecuteQuery/HReadFirst, the actual sql-statement is fired 2 or even 3 times! And that the client gets the recordset 2 or 3 times!

Will the native driver "solve" this? And is it for that reason that performance will be better, as some of you already noticed?
Second: do I have to rewrite (parts of) my code when switching to the native driver?

Arie
Reply Quote
kevinw
Re: SQL server native driver
June 03, 2008 06:29PM
I have noticed looking at the SQL Query Profiler that the WD H commands can vary what they send to the database server in comparison to what you would expect. SQLExec() seems to give more control.

Kevin
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: