Hello, I need some help 'selling' the idea to management that we should be using an the SQL OLEDB provider instead of the current ODBC one. The current web application (classic ASP) stores a single ODBC based connection string in a shared config file. All connections are created a via a common component using ADO so changes to considerable number of pages should be avoidable even if some code in the way the connection is created needs to change. The main concern is the behaviour of SET NOCOUNT OFF. With a the SQL OLEDB provider this can result in two result sets being returned the first simply contain a number of row affected. This of course will break lots of things and must be avoided. Is there something I put in the connection string or assign to the ADODB.Connection properies collection which will ensure that NOCOUNT ON is SET by default on the connection? Or will it take a roundtrip to the server to ensure that this and other session properties are configured before returning the connection to the caller? Where can I find a comparision of the performance between the two that can bolster my case? Does connection pooling vary between the two in any way that is advantageous? Thanks for your help, Anthony.