Hello

Does using SQLSetStmtOption with 'SQL_MAX_ROWS' option really help in
improving performance and reducing network traffic?
Have you noticed and drastic difference in performance by using this?

Shree

This has the same effect as using SET ROWCOUNT inside your statement and is
a fairly bad general coding practice, which might speed up you client
program, but puts the burden on the server, because it will have to execute
the complete SQL statement and throw away the remaining results, which is a
waste of resources on the server side.

Writing more selective SQL statements, or using the TOP operator will give
you a better performance on both the client and the server.

GertD@SQLDev.Net

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2003 All rights reserved.

"shree" <shreelak@hotmail.com> wrote in message
news:OFgq5DxnDHA.2200@TK2MSFTNGP12.phx.gbl...
> Hello
>
> Does using SQLSetStmtOption with 'SQL_MAX_ROWS' option really help in
> improving performance and reducing network traffic?
> Have you noticed and drastic difference in performance by using this?
>
> Shree
>
>