Data Points: Designing an Entity Data Model John Papa - February 2008 With the Entity Framework, developers are given more flexibility by being able to design around a conceptual model rather than a relational data model. To get started, you need to know how to design an Entity Data Model. John Papa walks you through that process.
Data Points: Data Binding in WPF John Papa - December 2007 WPF is one of the most important new technologies in the .NET Framework 3.0. This month John Papa introduces its data binding capabilities.
Data Points: Common Table Expressions John Papa - October 2007 In T-SQL, views and derived tables serve similar purposes and have their advantages. But when working with SQL Server 2005,there's a third option--using Common Table Expressions (CTEs). John Papa explains.
Data Points: SQL Server Management Objects John Papa - June 2007 SQL Server Management Objects offer developers a robust toolset for backing up and restoring databases, and issuing DDL commands, as John Papa explains.
Data Points: Revisiting System.Transactions John Papa - November 2006 The System.Transactions namespace of the Microsoft .NET Framework makes handling transactions much simpler than previous techniques. Read all about it this month.
Data Points: Using XQuery, New Large DataTypes, and More John Papa - March 2006 SQL Server 2005 introduces a lot of new features, but it also enhances the popular and oft-used Transact-SQL (T-SQL) language. Changes include the introduction of new datatypes to store large values using the MAX indicator, the integration of enhanced XML querying and data modification with XQuery, and the new XML datatype.
Data Points: DataSet and DataTable in ADO.NET 2.0 John Papa - November 2005 ADO. NET 2. 0 sports some exciting enhancements to the core classes found in ADO. NET 1. x and introduces a variety of new classes, all of which promise to improve performance, flexibility, and efficiency.
Data Points: The Enterprise Library Data Access Application Block, Part 3 John Papa - October 2005 E nterprise applications can have a wide variety of data update requirements. Sometimes you need to save multiple rows of changes at once within a single transaction. Other times, the user must be allowed to enter multiple rows of data, send them to the database in a batch; and if a row or two fails, only the rows that succeeded should be committed and remain committed.
Data Points: XML Features in SQL Server 2000 John Papa - June 2005 SQL Server™ 2000 includes several XML features that let you transform relational rowsets into hierarchical XML documents, read XML documents, and bulk load data via XML. For example, you can pass an XML document to a stored procedure, join the XML to some tables and return a rowset, or even modify data in the database.
Data Points: ADO.NET and System.Transactions John Papa - February 2005 The Microsoft® . NET Framework versions 1. 0 and 1. 1 represented major changes in software development. However, one important thing that did not change much was support for distributed transactions.
Data Points: Data Source Controls in ASP.NET 2.0 John Papa - January 2005 ASP. NET 2. 0 introduces a series of new tools that improve data access including several data source and data bound controls. The new assortment of data source controls can eliminate a ton of repetitive code that was required in ASP.
Data Points: Efficient Coding With Strongly Typed DataSets John Papa - December 2004 Someone once said to me that the hallmark of a good developer is the desire to spend time efficiently. Developers are continually pursuing ways to make coding easier and faster, and to reduce the number of errors.
Data Points: Handling Data Concurrency Using ADO.NET, Part 2 John Papa - October 2004 Enterprise development has been moving towards a discon-nected model in recent years and ADO. NET development is no exception. While the disconnected model of the ADO. NET DataSet offers great flexibility, that adaptability also means looser control over data updates than you get with a connected data access model.
Data Points: Handling Data Concurrency Using ADO.NET John Papa - September 2004 One of the key features of the ADO. NET DataSet is that it can be a self-contained and disconnected data store. It can contain the schema and data from several rowsets in DataTable objects as well as information about how to relate the DataTable objects—all in memory.
Data Points: Migrating from ADO to ADO.NET, Part 2 John Papa - August 2004 As you move forward with your use of ADO. NET, you'll need to know how to approach situations that you previously learned to handle in ADO and now have to tackle with ADO. NET. Just as n-tiered solutions developed using Visual Basic®, C++, and ASP often rely on ADO for their data access needs, Windows® Forms, Web Forms, and Web services rely on ADO.
Data Points: Migrating from ADO to ADO.NET John Papa - July 2004 In recent years ADO has taken the lead as the preferred method for implementing data access in Windows®-based applications. Huge numbers of ADO applications are in use today and many developers are well versed in ADO development.
Data Points: Techniques for Managing Rowset Paging John Papa - May 2003 There are a number of ways to handle paging in Web applications. This month I'll examine several paging techniques and weigh their pros and cons. John Papa discusses how to manage paging and caching issues through the lower tiers of an n-tiered architecture, including how to make SQL Server manage the paging on your app's behalf.
Data Points: Expressions in ADO.NET John Papa - January 2003 Managing relations in a database became a whole lot easier with ADO. NET. Instead of returning a single rowset to a data store, you can return a series of rowsets and relate them within a DataSet. There are numerous advantages to using related DataTables in ADO.
Data Points: DataRelations in ADO.NET John Papa - November 2002 One of the biggest differences between traditional ADO and ADO. NET is that the rowsets stored within ADO. NET can be truly relational. For example, a DataSet can store one DataTable containing customers and another DataTable containing the customers' orders.