|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Sql Native Client vrs SQLClient Namespace...I am just trying to bend my mind around this one, and would love any good
input to the subject. It seems that SQL2005 introduced a "new" way to access SQLServer with "SQL Native Client" and it is being promoted as a "Better Mouse trap" providing access to many new features in 2k5. However it also seems like this is a "COM" Object and as such should have greater overhead to any native .net client access lib. (SQLClient Namespace).. So... what should we use for performance? can sql namespace get past a raised error in a batch? i.e. Raiserror x ; select * from y;update z set c1=5 TIA Rob Ah, the new provider is designed for legacy COM applications (like VB6)--not
..NET applications. It exposes the new features of SQL Server 2005 to COM applications. It is not MDAC dependent so it should perform better. -- Show quote____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP INETA Speaker www.betav.com/blog/billva www.betav.com Please reply only to the newsgroup so that others can benefit. This posting is provided "AS IS" with no warranties, and confers no rights. __________________________________ "rob lynch" <robly***@discussions.microsoft.com> wrote in message news:4670249B-0DB9-4712-9B60-F42FDB00A745@microsoft.com... >I am just trying to bend my mind around this one, and would love any good > input to the subject. > > It seems that SQL2005 introduced a "new" way to access SQLServer with "SQL > Native Client" and it is being promoted as a "Better Mouse trap" providing > access to many new features in 2k5. However it also seems like this is a > "COM" Object and as such should have greater overhead to any native .net > client access lib. (SQLClient Namespace).. > > So... > what should we use for performance? > can sql namespace get past a raised error in a batch? i.e. Raiserror x ; > select * from y;update z set c1=5 > > > TIA > > Rob Thanks Bill,
that is pretty well what I was thinking.. but I thought I should check. Do you know if there is any work being done in SQLClient to enable "seeing" the continued processing that is possible after an error event occours.. I.e. Error then and update.. the update (and any other statements will occour, but the error prevents sqlclient from seeing any of it as the error becomes the boundary of what the client sees...) TIA Rob Show quote "William (Bill) Vaughn" wrote: > Ah, the new provider is designed for legacy COM applications (like VB6)--not > ..NET applications. It exposes the new features of SQL Server 2005 to COM > applications. It is not MDAC dependent so it should perform better. > > -- > ____________________________________ > William (Bill) Vaughn > Author, Mentor, Consultant > Microsoft MVP > INETA Speaker > www.betav.com/blog/billva > www.betav.com > Please reply only to the newsgroup so that others can benefit. > This posting is provided "AS IS" with no warranties, and confers no rights. > __________________________________ > > "rob lynch" <robly***@discussions.microsoft.com> wrote in message > news:4670249B-0DB9-4712-9B60-F42FDB00A745@microsoft.com... > >I am just trying to bend my mind around this one, and would love any good > > input to the subject. > > > > It seems that SQL2005 introduced a "new" way to access SQLServer with "SQL > > Native Client" and it is being promoted as a "Better Mouse trap" providing > > access to many new features in 2k5. However it also seems like this is a > > "COM" Object and as such should have greater overhead to any native .net > > client access lib. (SQLClient Namespace).. > > > > So... > > what should we use for performance? > > can sql namespace get past a raised error in a batch? i.e. Raiserror x ; > > select * from y;update z set c1=5 > > > > > > TIA > > > > Rob > > >  |
|||||||||||||||||||||||
Other interesting topics