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


Tip Topics

All Tips
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

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     

tips >> application development >> Performance Tuning SQL Server ODBC

Performance Tuning SQL Server ODBC

By : Brad McGehee
Feb 05, 2007

Page 2 / 2

While SQL Server application roles offer many benefits, they also cause a performance problem. Application roles cannot take advantage of ODBC connection pooling. Because of this, you may want to reconsider using application roles in your applications. [7.0, 2000, 2005] Updated 2-20-2006

*****

When you create a DSN for a SQL Server connection using the DSN Wizard, there is an option called "Save long running queries to the log file." Along with this option is the setting, "Long query time (milliseconds)." Both of these options can be used together to help you identify slow running queries in SQL Server applications that use a DSN for connecting to SQL Server. When you select this option and specify what you want as the long query time, those queries that exceed the time you enter will be logged to a file that you specify by name.

While this feature can be handy in some occasions, long running queries can also be identified using the SQL Server Profiler. One advantage of this feature over the Profiler is that is will generally take up less overhead when it runs than Profiler will. On the other hand, Profiler provides more detailed data than this feature. [6.5, 7.0, 2000, 2005] Updated 2-20-2006


<< 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