Sahil
Sun Mar 05 02:56:35 CST 2006
You could technically use the TDSParser internal class, if you really really
needed super custom code. For instance, if you needed to implement
UpdateBatchSize in your own business objects - not just DataAdapter, thats
how you'd do that.
But for 99.99% tasks, SqlCommand is as close to the metal as you'd want to
be.
- Sahil Malik [MVP]
ADO.NET 2.0 book -
http://codebetter.com/blogs/sahil.malik/archive/2005/05/13/63199.aspx
__________________________________________________________
<lbolognini@gmail.com> wrote in message
news:1141524061.929372.170760@i40g2000cwc.googlegroups.com...
>
> David Browne wrote:
>
>> The low-level interfaces to SQL Server are in the System.Data.SqlClient
>> and
>> System.Data.SqlTypes namespaces. Technically these are part of ADO.NET,
>> but
>> you can bypass DataSets and avoid (or control) the translation of data
>> from
>> SQL Server types to CLR types by working directly with the types in those
>> namespaces.
>>
>> There is no unmanaged library that offers better or more direct access to
>> SQL Server than these.
>
> Thanks David, much clearer now.
>
> Lroenzo
>