Re: SQL Server too slow

From: Erland Sommarskog (sommar_at_algonet.se)
Date: 12/27/03


Date: Sat, 27 Dec 2003 10:14:07 +0000 (UTC)

Murtix Van Basten (nospam@nospam.org) writes:
> How do I find out a database set to autoclose ?

For a single database you can do:

   exec sp_dboption db, 'autoclose'

To check all databases use:

   exec sp_helpdb

But since the autoclose information is hidden in the middle, this may
be simpler:

  select name from master..sysdatabases
  where databasepropertyex(name, 'IsAutoClose') = 1

You can also view it in Enterprise Manager, but it is left as an exercise
to the reader to find out how.

-- 
Erland Sommarskog, SQL Server MVP, sommar@algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp


Relevant Pages

  • Re: Slow initial record write
    ... 'autoclose' as 'off' so I guess this isn't the issue. ... directly to the SQL server and it was as follows: ... > To find out execute the following within Query Analyzer: ... > be due to the database starting up. ...
    (microsoft.public.sqlserver.setup)
  • Re: Slow initial record write
    ... > 'autoclose' as 'off' so I guess this isn't the issue. ... > directly to the SQL server and it was as follows: ... >> To find out execute the following within Query Analyzer: ... >> be due to the database starting up. ...
    (microsoft.public.sqlserver.setup)
  • Re: Speed of SQLExpress vs SQL2005
    ... If this is the first transaction you run and if you're the only one logging ... By default, SQL Express ... databases are autoclose to minimize resource usage. ... query you run after login on will take much longer because the database has ...
    (microsoft.public.sqlserver.setup)
  • Re: Sql server slow
    ... My autoclose suggestion might help Miles' EM database enumeration problem ... Slow connectivity can have many ... >> SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • Re: Repeated Starting up database messages
    ... Jonathan ... > Turn off autoclose for the database. ... > process got hold of the file while SQL Server didn't ... > tried to access the file, ouch!, suspect database. ...
    (microsoft.public.sqlserver.server)