Board index » delphi » Curiosity about TADODataset

2003-11-07 03:35:31 AM
delphi118
Does anyone out there use the SET NOCOUNT ON option when using a TADODatset?
TADODataset.CommandType := cmdText;
For instance;
SET NOCOUNT ON
SELECT *
FROM tmpCompanyProducts
WHERE CompanyProductsIndex IS NULL
Is this better than just;
SELECT *
FROM tmpCompanyProducts
WHERE CompanyProductsIndex IS NULL
Is there any benefit to this? I know that i include it in most of my sproc's
just to eliminate the extra bits being passed back across the network. Does
this have the same effect when using the TADODataset or TADOQuery?
Thanks for your time,
Brian
 

SQL Server returns the number of rows affected for a Transact SQL statement.
On SP executing a lot of statements it can generate a lot of extra traffic,
not in a single SQL sentence.
--
Guillermo Castaño A.
www.GrupoMillennium.com
"Brian Hollister" <bhollisterATfuturaintlDOTcom>writes

I realize that it is only a couple of bytes but I was just wondering if
anyone else does this as an optimization technique? Every 'bit' counts,
right?
"Guillermo Castaño A" <XXXX@XXXXX.COM>wrote in
message news:XXXX@XXXXX.COM...