- Full Description
Assuming only basic knowledge of C# 2008, Beginning C# 2008 Databases teaches all the fundamentals of database technology and database programming readers need to quickly become highly proficient database users and application developers.
A comprehensive tutorial on both SQL Server 2005 and ADO.NET 3.0, Beginning C# 2008 Databases explains and demonstrates how to create database objects and program against them in both TSQL and C#. Full of practical, detailed examples, its been fully revised and updated for C# 2008 and offers the most complete, detailed, and gentle introduction to database technology for all C# programmers at any level of experience.
- Comprehensively and concisely explains fundamental database concepts and programming techniques
- Rich in working examples of both TSQL and C# programs
- Covers all the features most database programming ever requires
What youll learn
- How relational databases work and how to use them
- How C# uses ADO.NET to access databases
- How to write stored procedures in TSQL and call them from C# programs
- How to use XML in database applications
- How to use LINQ to simplify C# database programming
- How to install SQL Server 2005 Express and Visual C# 3.0
- Express and use them to teach yourself database programming by doing it
Who this book is for
Beginning C# 2008 Databases is for every C# programmer. Database programming requires relatively little knowledge of C# but a lot of knowledge about relational database concepts and the database language SQL. This book assumes no prior database experience and teaches you, always through handson examples, how to create and use relational databases with SQL and how to access them with C#. Almost every application needs to access a database, and this book teaches all the fundamentals you needand may ever needto develop professional database applications.
- Source Code/Downloads
Please Login to submit errata.On page 29:In the 7th bullet point, the book states: "In RDBMSs, a transaction either commits all the changes or rolls back all the actions performed till the point at which failure occurred."
This is seriously wrong. If there is a failure, all the steps are rolled back to the point where the transaction started. Otherwise some of the steps will take place (up to the failure point), but others won't (after the failure point) and the database will be left in an inconsistent state.