After my last book, Essential ADO.NET, was handed in to the publisher 10 days
before .NET 1.0 shipped, I swore I'd never write another. To keep up with a
technology while it was developing and the product features were being
refined on an almost daily basis was too big of an energy sink. Then, less
than a year later, I caught wind of a new version of SQL Server, codenamed
Yukon. Like each version of SQL Server before it, there were lots of features
for DBAs, high-availability features, tuning features, scalability features,
and so on. A fast growing field called Business Intelligence being developed
on SQL Server was on the cusp of this. But the biggest changes that caught my
eye were those in the developer area. I was hooked.
Transact SQL serves developers well and there are many enhancements to it in
SQL Server 2005. But in the last few years, I'd been spending a l... (more)
In this "Data Access" column, I will discuss topics relating to the Microsoft
.NET data access stack, known as ADO.NET. This installment starts with an
overview of the different pieces of the stack and finishes with an
interesting development in the world of SQL Server, .NET, and XML Web
services.
The ADO.NET data access APIs consist of three types of classes:
1. Classes for executing database commands in connected mode: This is
accomplished by a series of data providers that run in managed code as much
as possible. Each of these data providers implements approximately the same ... (more)
Bob Beauchemin is a course author and instructor for DevelopMentor. He's been working in the industry for more than 22 years, writing database applications most of that time. He's written Java code using Oracle 8i, DB/2 UDB, Sybase, and SQL Server and worked on DevelopMentor's Java curriculum.
Sue Poremba
Scott Sellers
Anthony Franco
Daniel Morris
Wayne Walls
Niki Acosta
Jereme Hancock
Oren Michels
Marvin Wheeler
Douglas Kim
