ADO.NET versus T-SQL versus XML

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

If dealing in an environment with all SQL database environment, should I
use ADO.NET or T-SQL? If in a multidatabase environment, should ADO.NET be
used in preference to XML?
 
Huh? This makes very little sense. TSQL is the query language used by most
editions of SQL Server, ADO.NET is the data access interface used to execute
TSQL queries, and XML is a data transport/data storage specification. I
expect you should do some additional reading...

--
____________________________________
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.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
 
I agree that I should do more reading about this, I am very new to ADO.NET.
It was just a question that came to mind as I was starting to read ADO .NET
Programming by Terrence J. Joubert and Ryan N. Payet. It seems that ADO.NET
can be used to manipulate data in client applications. E.g. setting up query
strings and executing them and I was just wondering when ADO.NET should be
used and when T-SQL should be used.

Iam wondering if "Professional ADO.NET 2: Programming with SQL Server 2005,
Oracle, and MySQL" by Wallace B. McClure would be better starting point for
ADO.NET.

What would your recommendation be?
 
I expect Wally's book would be fine if you were not sure which platform
you're targeting. My latest book is really designed for those getting
started with SQL Server (and just SQL Server). While it might help build
properly architected applications for other platforms, it really gets into
detail on all the aspects of building SQL Server applications.

TSQL should be used to write stored procedures that are deployed to the
database and remain in place for all clients to use. ADO.NET is simply a
pathway to those procedures. In the book I drone on and on about how the
Visual Studio tools can be used to generate ADO.NET--especially when
accessing tables directly. However, you'll find that most pro shops have
outgrown that approach. They block access to the base tables and expose
Views and SPs instead.

In any case, when working with SS, you'll want to (need to) learn both the
ADO.NET data access interface and TSQL--the SS query language.

hth

--
____________________________________
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.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------
 
Back
Top