Site sponsored by: Idera Try Idera’s new SQL admin toolset
SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • Quiz
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


Article Topics

All Articles
Performance Tuning
Audit
Business Intelligence
Clustering
Reporting Services
Developer
General DBA
ASP.NET / ADO.NET

Write for Us

Share you SQL Server knowledge with others and raise your profile in the community More...
Latest Articles

Policy Based Management in SQL Server 2008
Inside SQL Server Cluster Setup and Troubleshooting Techniques - Part I ...
Configure and Manage Policy Based Management in SQL Server 2008 ...
Using Column Sets with Sparse Columns

More     
 
Latest FAQ's

Cannot Start SQL Server Service
Users are able to connect to report manager but not able ...
Errors when SQL Server Snapshot Replication is Running
How to Display Server Name or IP Address in a Reporting ...

More     
   
Latest Software Reviews

Spotlight on ApexSQL Doc 2008
ApexSQL Enforce
Embarcadero Change Manager
SQL Server DBA Dashboard

More     

articles >> developer >> Exposing API Server Cursors

Exposing API Server Cursors

By : Sean Robert Fitzgerald
Oct 25, 2006

Page 2 / 2


OPENQUERY

 SQL Server has a built-in function which is used to ensure that the processing of the distributed query is performed against the remote server.  Please refer to the OPENQUERY topic in SQL Server Books Online for additional information relating to this function. 

The use of the API Server Cursor was eliminated by simply revising the query to utilize the OPENQUERY function.

use LocalDatabase;
select  *
from    OPENQUERY(
          RemoteServer
          , 'select *
                   from RemoteDatabase.dbo.RemoteTable0 as t0
                   inner join       RemoteDatabase.dbo.RemoteTable1 as t1
                             on      t0.Account = t1.Account
                   where  t0.Account = ''XYZ'''
); 


The results of another SQL Server Profiler trace denote that the SELECT statement identified in the OPENQUERY function is the only statement that is executed on the remote server.  This significantly reduces the amount of resources that are utilized to support the execution of this query.

Conclusion

In this article, I’ve tried to provide a brief overview of what an API Server Cursor is, how to identify when a distributed query is utilizing an API Server Cursor, and provide an example of a simple distributed query that eliminates the usage of the API Server Cursor.  Thankfully, SQL Server provides all of the tools that you need to eliminate the use of an API Server Cursor from your distributed queries.  Good luck!

Reference

API Server Cursors
OPENQUERY
SQL Server 2000 Operations Guide
System Stored Procedures (Transact-SQL)


<< Prev Page         








Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | QDPMA Performance Tuning | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views


              © 1999-2008 by T10 Media. All rights reserved