• subscribe
January 22, 2003 12:00 AM

30-Second Timeout

SQL Server Pro
InstantDoc ID #37582

If you're following the techniques described in the main article, you might want to simplify the process of connecting to the System Monitor—generated tables by using Microsoft Access data access pages to query the tables directly. However, you'll probably find that queries you create access unindexed data, making them run especially slow. Additionally, data access pages seem to have a bug; they won't accept the Connect Timeout property and instead use a default timeout of 30 seconds. So if you use data access pages to view System Monitor—logged data, you need to perform some data transformation to avoid the 30-second limitation. We suggest you create an alternate data repository in SQL Server in which you can store and manipulate the System Monitor data to suit your needs—and avoid the 30-second limitation.



ARTICLE TOOLS

Comments
  • Robert
    6 years ago
    Feb 13, 2006

    useless

  • Dave
    9 years ago
    Jan 27, 2003

    Awww, no code on the site for this article?

You must log on before posting a comment.

Are you a new visitor? Register Here
  • SP1?
    I know there is a SP1 for SQL 2008 R2 available....and there is a "feature pack" as well... ...
  • SQL database mirroring
    I have SQL Server 2008 R2 Enterprise 64bit on Windows 2008 R2 Enterprise 64bit.  Each SQL Server has...
  • Dell Compellent Disk Drive
    Does anybody has experience with Dell Compellent Disk Drive? Basically, this system manages all disk...
  • Sql server performance tuning
    I need to find a tool that help me to optimize sql server,queries,improve the performance and solve ...