June 2, 2005 at 2:57 am
Hi from time to time we have some suspect problems. No it seems to be the time of the year 😉
Please find herewith the log :
2005-06-02 06:30:21.06 spid56 Starting up database 'SO'.
2005-06-02 06:30:21.68 spid56 Starting up database 'testepp'.
2005-06-02 06:30:22.31 spid56 Starting up database 'testepp'.
2005-06-02 06:30:22.70 spid56 Starting up database 'testepp'.
2005-06-02 06:30:23.10 spid56 Starting up database 'testepp'.
2005-06-02 06:33:00.83 spid56 Starting up database 'SB'.
2005-06-02 06:49:00.46 spid55 Starting up database 'EPP'.
2005-06-02 06:50:02.67 spid55 Starting up database 'CCVAgora'.
2005-06-02 06:50:05.05 spid55 Starting up database 'SB'.
2005-06-02 06:50:05.46 spid55 Starting up database 'SO'.
2005-06-02 06:50:06.03 spid55 Starting up database 'testepp'.
2005-06-02 06:50:08.19 spid56 Starting up database 'CCVAgora'.
2005-06-02 06:50:09.41 spid56 Starting up database 'EPP'.
2005-06-02 06:50:10.00 spid56 Starting up database 'MIDAS'.
2005-06-02 06:50:10.47 spid56 Starting up database 'SB'.
2005-06-02 06:50:10.85 spid56 Starting up database 'SO'.
2005-06-02 06:50:11.46 spid56 Starting up database 'testepp'.
2005-06-02 06:50:12.08 spid56 Starting up database 'CCVAgora'.
2005-06-02 06:50:13.61 spid56 Starting up database 'CCVAgora'.
2005-06-02 06:50:14.82 spid56 Starting up database 'EPP'.
2005-06-02 06:50:15.44 spid56 Starting up database 'EPP'.
2005-06-02 06:50:15.81 spid56 Starting up database 'EPP'.
2005-06-02 06:50:16.19 spid56 Starting up database 'EPP'.
2005-06-02 06:50:16.60 spid56 Starting up database 'MIDAS'.
2005-06-02 06:50:17.02 spid56 Starting up database 'MIDAS'.
2005-06-02 06:50:17.45 spid56 Starting up database 'MIDAS'.
2005-06-02 06:50:17.94 spid56 Starting up database 'MIDAS'.
2005-06-02 06:50:18.33 spid56 Starting up database 'SB'.
2005-06-02 06:50:18.74 spid56 Starting up database 'SB'.
2005-06-02 06:50:19.10 spid56 Starting up database 'SB'.
2005-06-02 06:50:19.52 spid56 Starting up database 'SB'.
2005-06-02 06:50:19.88 spid56 Starting up database 'SO'.
2005-06-02 06:50:20.91 spid56 Starting up database 'SO'.
2005-06-02 06:50:21.52 spid56 Starting up database 'testepp'.
2005-06-02 06:50:22.16 spid56 Starting up database 'testepp'.
2005-06-02 06:50:22.53 spid56 Starting up database 'testepp'.
2005-06-02 06:50:22.97 spid56 Starting up database 'testepp'.
2005-06-02 06:50:29.67 spid59 Starting up database 'CCVAgora'.
2005-06-02 06:54:33.10 spid55 Starting up database 'CCVAgora'.
2005-06-02 07:10:03.70 spid55 Starting up database 'CCVAgora'.
2005-06-02 07:10:04.99 spid55 Starting up database 'EPP'.
2005-06-02 07:10:05.60 spid55 Starting up database 'MIDAS'.
2005-06-02 07:10:06.03 spid55 Starting up database 'SB'.
2005-06-02 07:10:06.43 spid55 Starting up database 'SO'.
2005-06-02 07:10:07.03 spid55 Starting up database 'testepp'.
2005-06-02 07:10:09.26 spid56 Starting up database 'CCVAgora'.
2005-06-02 07:10:10.48 spid56 Starting up database 'EPP'.
2005-06-02 07:10:11.12 spid56 Starting up database 'MIDAS'.
2005-06-02 07:10:11.56 spid56 Starting up database 'SB'.
2005-06-02 07:10:12.10 spid56 Starting up database 'SO'.
2005-06-02 07:10:12.70 spid56 Starting up database 'testepp'.
2005-06-02 07:10:13.31 spid56 Starting up database 'CCVAgora'.
2005-06-02 07:10:14.82 spid56 Starting up database 'CCVAgora'.
2005-06-02 07:10:16.03 spid56 Starting up database 'EPP'.
2005-06-02 07:10:16.64 spid56 Starting up database 'EPP'.
2005-06-02 07:10:16.98 spid56 Starting up database 'EPP'.
2005-06-02 07:10:17.37 spid56 Starting up database 'EPP'.
2005-06-02 07:10:17.78 spid56 Starting up database 'MIDAS'.
2005-06-02 07:10:18.18 spid56 Starting up database 'MIDAS'.
2005-06-02 07:10:18.59 spid56 Starting up database 'MIDAS'.
2005-06-02 07:10:18.98 spid56 Starting up database 'MIDAS'.
2005-06-02 07:10:19.46 spid56 Starting up database 'SB'.
2005-06-02 07:10:19.84 spid56 Starting up database 'SB'.
2005-06-02 07:10:20.21 spid56 Starting up database 'SB'.
2005-06-02 07:10:20.60 spid56 Starting up database 'SB'.
2005-06-02 07:10:20.96 spid56 Starting up database 'SO'.
2005-06-02 07:10:21.88 spid56 Starting up database 'SO'.
2005-06-02 07:10:22.49 spid56 Starting up database 'testepp'.
2005-06-02 07:10:23.10 spid56 Starting up database 'testepp'.
2005-06-02 07:10:23.54 spid56 Starting up database 'testepp'.
2005-06-02 07:10:23.95 spid56 Starting up database 'testepp'.
2005-06-02 07:25:01.48 spid56 Starting up database 'EPP'.
2005-06-02 07:30:02.66 spid55 Starting up database 'EPP'.
2005-06-02 07:32:00.47 spid55 Starting up database 'SB'.
2005-06-02 07:35:01.46 spid55 Starting up database 'EPP'.
2005-06-02 07:39:11.95 spid62 Starting up database 'CCVAgora'.
2005-06-02 07:41:00.53 spid56 Starting up database 'MIDAS'.
2005-06-02 07:51:50.43 spid55 Starting up database 'CCVAgora'.
2005-06-02 08:10:40.83 spid56 DBCC TRACEON 208, server process ID (SPID) 56.
2005-06-02 08:10:50.61 spid56 Starting up database 'CCVAgora'.
2005-06-02 08:24:11.71 spid69 Starting up database 'CCVAgora'.
2005-06-02 08:24:38.68 spid69 Starting up database 'CCVAgora'.
2005-06-02 08:29:15.59 spid60 Starting up database 'CCVAgora'.
2005-06-02 08:33:59.55 spid62 DBCC TRACEON 208, server process ID (SPID) 62.
2005-06-02 09:00:58.38 spid85 Starting up database 'CCVAgora'.
2005-06-02 09:13:30.35 spid56 Starting up database 'CCVAgora'.
2005-06-02 09:24:13.02 spid79 Starting up database 'CCVAgora'.
2005-06-02 09:29:53.31 spid74 Starting up database 'CCVAgora'.
2005-06-02 09:36:20.18 spid58 Starting up database 'CCVAgora'.
2005-06-02 09:43:22.87 spid56 Starting up database 'CCVAgora'.
2005-06-02 09:44:18.52 spid68 Starting up database 'CCVAgora'.
2005-06-02 09:50:22.94 spid56 Starting up database 'CCVAgora'.
2005-06-02 10:00:19.35 spid58 DBCC TRACEON 208, server process ID (SPID) 58.
2005-06-02 10:00:24.56 spid58 Starting up database 'CCVAgora'.
2005-06-02 10:01:49.03 spid64 DBCC TRACEON 208, server process ID (SPID) 64.
2005-06-02 10:07:30.28 spid59 Starting up database 'CCVAgora'.
2005-06-02 10:09:39.79 spid59 Starting up database 'CCVAgora'.
2005-06-02 10:16:23.18 spid58 Starting up database 'CCVAgora'.
2005-06-02 10:16:33.76 spid58 DBCC TRACEON 208, server process ID (SPID) 58.
2005-06-02 10:36:00.36 spid78 Starting up database 'SO'.
2005-06-02 10:36:00.97 spid78 Starting up database 'testepp'.
2005-06-02 10:36:01.74 spid78 Starting up database 'CCVAgora'.
2005-06-02 10:36:03.17 spid78 Starting up database 'SO'.
2005-06-02 10:36:04.03 spid78 Starting up database 'testepp'.
2005-06-02 10:36:04.71 spid78 Starting up database 'CCVAgora'.
2005-06-02 10:36:06.19 spid78 Starting up database 'CCVAgora'.
2005-06-02 10:36:07.44 spid78 Starting up database 'SO'.
2005-06-02 10:36:08.47 spid78 Starting up database 'SO'.
2005-06-02 10:36:09.05 spid78 Starting up database 'testepp'.
2005-06-02 10:36:09.72 spid78 Starting up database 'testepp'.
2005-06-02 10:36:10.22 spid78 Starting up database 'testepp'.
2005-06-02 10:36:10.72 spid78 Starting up database 'testepp'.
2005-06-02 10:37:55.13 spid56 Starting up database 'CCVAgora'.
and so it goes on. Anybody any idea what's going on, and how to stop it 😉
Thx in advance
J
JV
June 2, 2005 at 6:13 am
It looks to me like you have the 'autoclose' database option turned on? (see sp_dboption)
/Kenneth
June 2, 2005 at 6:24 am
Yes indeed. I now turned it off.
What is the function of autoclose ?
Many thx
J
JV
June 2, 2005 at 6:27 am
Kenneth
What about the auto update stats and auto create stats ?
Thx
J
JV
June 2, 2005 at 6:41 am
From BOL
| autoclose | When true, the database is shutdown cleanly and its resources are freed after the last user logs off. |
You don't want to have autoclose enabled on any production system.
/Kenneth
June 2, 2005 at 6:44 am
Personally, I recommend that you start by having these enabled. Only if you run into problems that may be related to the maintenance of index stats should they be of any concern. I've been running with these enabled for years without noticing any penalties. Naturally this may vary from system to system - but I do think it's a good idea to start with them enabled.
/Kenneth
June 2, 2005 at 11:13 am
Turn torn page detection off, if enabled.
June 3, 2005 at 8:40 am
Why turn off torn page detection? It caught an issue on my production DB. I run CHECKDB nightly, and everything was fine. Midday, I got an email about a torn page. Got everyone out of the system, fixed the problem and let them back in. No data loss, no restores.
Terry
June 3, 2005 at 6:58 pm
This option does not prevent torn pages, it only tells you if you have one. Once it discovers one, your database is marked
as corrupt, and all you can do is to restore your database with your latest backup.
June 6, 2005 at 6:58 am
It doesn't mark the database as corrupt. It does tell you that there is a problem. I had to drop and rebuild an index recently to correct a problem that was flagged as a torn page but in reality wasn't.
Terry
April 10, 2007 at 2:44 pm
THANK YOU!
I just ran into a database that had hundreds and hundreds of such "starting up database ..." messages! Yep, AutoClose is on. And it's a production system. *sigh*
If the job were easy, we wouldn't get paid the big bucks (in a parallel dimension very much like our own).
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply