Streamline your Data Connections by Moving to MARS
Wecome to MARS. Here on MARS you can perform multiple database queries on a single connection. The code on MARS is simpler and easier to read. And you can conserve memory use and eliminate performance bottlenecks in data-intensive Web applications. Aren't you glad you gave MARS a try?
by Laurence Moroney
December 12, 2005
ultiple Active Result Sets (MARS) is a new feature of ADO.NET 2.0 that allows multiple queries or stored procedures to be performed on a single connection. The result of this is that you can get and manage multiple, forward-only, read-only result sets on a single connection. Prior to MARS, each result set required a separate connection. Of course, you'd have to manage those connections and resign yourself to the obvious costs in memory and the potential for bottlenecks in high-traffic applications—particularly in data-intensive Web applications.
The first commercial database to support MARS is SQL Server 2005, and in this article you'll get a primer on how to use this powerful, yet easy addition to the ADO.NET arsenal.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
ultiple Active Result Sets (MARS) is a new feature of ADO.NET 2.0 that allows multiple queries or stored procedures to be performed on a single connection. The result of this is that you can get and manage multiple, forward-only, read-only result sets on a single connection. Prior to MARS, each result set required a separate connection. Of course, you'd have to manage those connections and resign yourself to the obvious costs in memory and the potential for bottlenecks in high-traffic applications—particularly in data-intensive Web applications.
