|
|
|
|
|
|
| | Total Hits: 44 | Today: 0 | Author: Bob Beauchemin | Rating:  |
| | 
Microsoft ADO.NET is a database-general API. It is an API in which database vendors write plug-in data providers for their databases, such as OLE DB/ADO (providers), ODBC (drivers), or JDBC (drivers). It is not an API with a database-specific set of functions such as dbLib, or a database-specific object model such as OO4O (Oracle Objects for OLE). Predecessors of ADO.NET factored their providers into sets of interfaces, defined by a strict specification. For example, each OLE DB provider writer ... |
| | Total Hits: 45 | Today: 0 | Author: John Papa | Rating: |
| |
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. There have even been some major changes throughout the lifecycle of the pre-beta and beta versions of ADO.NET 2.0, such as the improvements to the new batch updating process. With the final release of ADO.NET 2.0 fast approaching and the feature set becoming more stable, it's time to take a closer... |
| | Total Hits: 40 | Today: 0 | Author: Pablo Castro | Rating: |
| |
In the 2.0 release of ADO.NET, we not only wanted to make existing scenarios easier, but also enable new scenarios that either were just not possible before, or were far from ideal. Asynchronous command execution is a good example of that. In releases of ADO.NET before 2.0, it wasn't possible to execute a command and not wait for it to complete before continuing execution. The addition of an asynchronous API enables scenarios where it is important for the application to continue execution withou... |
| | Total Hits: 46 | Today: 0 | Author: Bob Beauchemin | Rating: |
| |
ADO.NET 2.0 comes with a plethora of new features. This includes a new base-class-based provider model and features that all providers can take advantage of, as well as changes that are specific to System.Data.SqlClient. Because the .NET Framework 2.0 is being released in conjunction with SQL Server 2005, some of these features require SQL Server 2005 to be usable. This article is meant to serve as an overview and roadmap of the new features, give examples of their use, and includes a chart of w... |
| | Total Hits: 66 | Today: 0 | Author: Bipin Joshi | Rating: |
| |
Let's accept the real world fact that you need to write applications targeting not only SQL Server but also many other databases including MS-Access, Oracle and other ODBC databases. Classic ADO was a generic object model. You used to use the same Connection class with SQL Server, Access and Oracle. In ADO.NET, however, you need to use different classes depending on the provider you are using. That means before starting the coding phase you need to be aware of target database. If you develop an ... |
| | Total Hits: 118 | Today: 0 | Author: Jackie Goldstein | Rating:  |
| |
In this article, I will focus on developing with these and derived classes from within the Microsoft Visual Studio 2005 development environment. In particular, this article discusses the changes to the typed DataSet and the new typed TableAdapter that are generated by Visual Studio 2005. This article also looks at the designers and tools that offer tremendous flexibility and productivity for developing the data-centric aspects of your application. In order to explain the different concepts and f... |
| | Total Hits: 59 | Today: 0 | Author: Thiru Thangarathinam | Rating:  |
| |
One of the new features of ADO.NET 2.0 is the ability to create provider-independent data access code that enables you to code against a set of base abstract classes without referencing provider-specific classes. The key advantage of this approach is that it gives you the option of seamlessly working with multiple providers like SqlClient, OleDb, and ODBC without having to lock into a specific implementation. To this end, ADO.NET 2.0 provides a new namespace named System.Data.Common that exposes... |
| | Total Hits: 8 | Today: 0 | Author: Bob Beauchemin | Rating: |
| |
Any non-trivial relational database application is bound to have a lot of lookup tables. If you code graphical user interfaces as a specialty, you know these as the lists that populate the drop-down list boxes. I categorize lookup tables into two types: read-only tables and read-mostly tables. The difference is what can cause those tables to change. I think of a table as read-only if it takes a staff meeting or user meeting to change them. A good example is a table that contains categories of a ... |
| | Total Hits: 10 | Today: 0 | Author: ExtremeExperts.com | Rating:  |
| |
In this article, i am going to talk about some of the new features of ADO.NET 2.0. I just started working on ADO.NET 2.0. So this is just an starting, I will keep updating this article as when i find anything interesting in ADO.NET 2.0. If you think about ADO.NET 1.x DataSet, the major problem which comes to our mind is DataSet Serialization. Microsoft has worked lots on this part and they have improved the performance of Serialization a lot. In ADO.NET 1.x, Serialization of DataSet will happen... |
| | Total Hits: 12 | Today: 0 | Author: William Ryan | Rating: |
| |
It seems like just yesterday that Microsoft introduced a brand new data access technology that brought a ton of power as well as a decent sized learning curve. When ADO 2.xxx turned into ADO.NET, things changed dramatically. It took some getting used to to feel comfortable using the whole 'disconnected' model, but the "cool" factor made it all worth while. When .NET Framework 1.1 came out, very little changed in regard to what you needed to learn or what you could do with it. Well, we're turning... |
| | Total Hits: 8 | Today: 0 | Author: Mahesh Chand | Rating: |
| |
Bulk copying of data from one data source to another data source is a new feature added to ADO.NET 2.0. Bulk copy classes provides the fastest way to transfer set of data from once source to the other. Each ADO.NET data provider provides bulk copy classes. For example, in SQL .NET data provider, the bulk copy operation is handled by SqlBulkCopy class, which is described in Figure 1. As you can see from Figure 1, data from a data source can be copied to one of the four types - DataReader, DataSet... |
| | Total Hits: 13 | Today: 0 | Author: Mahesh Chand | Rating:  |
| |
This article summarizes the new and updated features of ADO.NET 2.0, which ships with .NET Framework 2.0. In my following articles I will discuss these features in more details with sample examples.... |
| | Total Hits: 75 | Today: 0 | Author: Mahesh Chand | Rating: |
| |
In ADO.NET 2.0, there is a new addition of DB provider factory classes, which allow developers to get the information about the data providers available (installed) on a machine. DbProviderFactories class's GetFactoryClasses method returns all the available data providers and GetFactory method returns the information about that specific provider.... |
| | Total Hits: 16 | Today: 0 | Author: Alex Homer | Rating: |
| |
ADO.NET 2.0 includes an extremely useful set of providers that you can use dozens of ways to quickly and accurately query your SQL Server or JET database. This article shows you how to be the pied piper of your metadata using the Schema API.... |
| | Total Hits: 4 | Today: 0 | Author: Alex Homer | Rating: |
| |
ADO.NET 2.0 includes an extremely useful set of providers that you can use dozens of ways to quickly and accurately query your SQL Server or JET database. This article shows you how to be the pied piper of your metadata using the Schema API.... |
| | Total Hits: 4 | Today: 0 | Author: Sahil Malik | Rating: |
| |
In this article Sahil Malik will explain some of the significant changes that have taken place for ADO.NET version 2.0. The article will cover improvements to serialization, the better streaming support and - in some cases - lower memory requirements associated with the DataTable, as well as new support for asynchronous command execution and better support for transactions via System.Transaction classes.... |
| | Total Hits: 10 | Today: 0 | Author: Amit Kumar Agrawal | Rating: |
| |
ADO.NET class libraries are used for accessing data from a wide range of data sources. One of the best features in ADO.Net is DataSet.Even though it was an exciting feature, performance was a concern with DataSet. Lets look some changes made to DataSet in ADO.Net in this article.... |
| | Total Hits: 20 | Today: 0 | Author: Mark Strawmyer | Rating: |
| |
In one of my early .NET Nuts & Bolts columns, I wrote about database-independent data access. The article basically demonstrates the use of the factory design pattern to decide at runtime which specific instances of database-related objects to create. It was a necessary evil for those of us unfortunate enough to have to move between different databases such as SQL Server and Oracle and not wanting to produce a bunch of provider-specific code in case the database changed (I'm convinced there's a ... |
| | Total Hits: 176 | Today: 0 | Author: Thiru Thangarathinam | Rating: |
| |
One of the new features of ADO.NET 2.0 is the ability to create provider-independent data access code that enables you to code against a set of base abstract classes without referencing provider-specific classes. The key advantage of this approach is that it gives you the option of seamlessly working with multiple providers like SqlClient, OleDb, and ODBC without having to lock into a specific implementation. To this end, ADO.NET 2.0 provides a new namespace named System.Data.Common that exposes... |
| | Total Hits: 15 | Today: 0 | Author: Bob Beauchemin | Rating: |
| |
Learn how to use the new notification technologies in ADO.NET 2.0 and SQL Server 2005 to handle ad-hoc data refreshes.... |
|
|
|
|
|
|