Database Design

Microsoft ADO.NET (Core Reference)

Format: Hardcover
Author: David Sceppa
ReleaseDate: 15 May, 2002
Publisher: Microsoft Press
Rating:

Not to be confused with Rebecca's Riordan's
NET out there. This is the best ADO. Do not confuse this with Rebecca's (that would be a tragedy).

This has in-depth coverage and has helped me so much, I can't thank David Sceppa enough. I look forward to his 2005 coverage and I hope it is as good as this.

.

Some good information, but too scattered to be useful
. I like some parts of this book.. I really do. But time and time again, when I need an example of how to do something, I have to go to many different sections to find the information.

I wish the book was structured in more segmented blocks. Give me one clear section on Datasets. Give me a clear section on DataAdapters, etc.

In the Dataset chapter, the author INSISTS on using a DataAdapter throughout the chapter. Everything is then based on that, forcing me to hunt and peck everywhere for an example on how to add data from an XML file, for example (which is extremely easy. . . one line of code. . . so it shouldn't take me dozens of pages to find the info).

If I were writing the chapter, I would start out with a top-down approach of all of the different ways a dataset could be used, what it is, etc. I would partition the chapter by sticking in the front of the chapter an "about" datasets part, followed by a top down "loading data" part, then "retrieving data" part.

I would expand the examples to be more meaningful. I find the scant examples making me desperate for more useful information during a project i am developing. I admit it. . I don't know much about datasets, but my usage of them is a heck of a lot simpler than the author makes them out to be. MUST I use a data adapter (I didn't when I did it). And if I SHOULD use a data adapter, EXPLAIN to me why I should use it. Don't just use it everywhere and not tell me why!

Does the author expect me to read the book from cover to cover before even attempting to think about developing a solution? I don't develop that way. I use books as reference guides.

Typically, when I develop using ADO. Net, I grab this book and try to find information I need. Inevitably, I do not, so I refer to Francesco Balena's fantastic VB. Net book. I end up using that to get me through my rough spots.

Ado. Net does serve to give me tidbits of useful information. But that is sad, because this book could be so much more if it followed Balena's method of information presentation.

To sum up my frustrations, in the DataAdapter chapter, the author begins by showing us a simple example of filling a dataset without a data adapter. I think this is very clear, very simple and clean. It is procedural and not much code. Coming from ADO, this makes more sense than does the concept of a data adapter. This is good, right? We have a simple example on how to fill a dataset. My first question is. . . why isn't this in the dataset chapter? Well it must be because the author thinks this is inferior to using data adapters. Ok fine, if that is true, EXPLORE THAT in the dataset chapter. At least get me up and running with *something*. This is the real world. . . not a perfect world. I am impressed with Sceppa's knowledge and ideology, but when I need to get up and running with a simple example, the last thing I need is philosophising on a deadline. This goes back to my earlier point. . . that this book must have been intended to be read cover to cover. I disagree with that approach. This is not a Tom Clancy novel. It is a technical reference book.

Another annoyance is the extensive usage of bold text for tiny page sections. It's very distracting to try to read 10pt non-bold text on a page that has 5 huge bold fonts screaming at you to read them.

If I did not own the book, I would not buy it. I would use Balena's book or go online for the information.

Not for the ADO novice but for those with a little hands on.
1 year, I had been utilizing ADO. For approx.NET in a limited way. It confused me the switch from ADO to ADO. NET and I wasn't that strong on ADO to begin with, so I dug my feet in about learning the rest. Then one faithful day I hit a wall in my abilities with ADO. NET. The trusty READER wasn't going to bail me out and only VIEWING data in a DATAGRID wasn't going to cover my hiney either. They wanted to modify the data. They wanted to delete data. They wanted POWER. . . .
(Shaking in fear. . . ) Really LEARN ADO. NET????!!!!

I looked through many ADO. NET books and found this one for me was easier to read. He gives a indepth explaination on each of the components in their respective chapters. While he only utilizes the OLEDB and SQL connections, the explaination he gave regarding using OLEDB over ODBC was convincing for me to switch.
I learned more about the DataAdapter than I had thought existed and now enjoy playing with ADO. NET. It really has empowered me.

While the code he gives is not for complete programs, but to accomplish the mission he is discussing. So, when you read the code. Don't expect to be building a program. Expect to be learning how to accomplish a task by looking at the section of code that handles it.

I recommend this book to any one who has a limited experience with ADO. NET and feels that it is time to expand their knowledge to fully embrace the power of . NET

(I know this recommendation comes at the closing of a chapter. The ADO. NET has been replaced by its 2. 0 version. We are still currently programming in Studio 2003. If the 2005 book meets the level of this - you will learn from it!).