May 8, 2003 at 1:57 am
At startup I get the following msg in the SQLserver 2000 errolog:
'Analysis of database 'dbname' (10) is 100% complete'
Exactly what does SQLserver do and why? I only get it on some databases?
May 8, 2003 at 6:57 am
Are you sure you don't have any jobs running on startup?
Darren
Darren
May 13, 2003 at 1:11 am
No, there are no jobs scheduled to run at startup and also no sp's which are executed at startup!
May 13, 2003 at 4:38 am
Might be wrong and cannot find any of my servers with this on it. But I believe if the ox stops unexpectedly it actually is checking the DBs for potential suspect issues such as file corruption. Did the server restart all of a sudden that day?
May 13, 2003 at 4:55 am
No, OS has been running for weeks......
And there are 12 databases on this server, but this 'check' was only done for 4 of them - db_options for these 4 are also not different from the others.
May 13, 2003 at 5:15 am
Anything occurr such as a close db action or an error occurr around in the error log at that time? And did you check Event Viewer to see if anything there around that time?
May 13, 2003 at 6:09 am
No, nothing in the eventlogs either.
This is it:
2003-05-08 07:40:22.08 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
2003-05-08 07:40:22.08 server Copyright (C) 1988-2002 Microsoft Corporation.
2003-05-08 07:40:22.08 server All rights reserved.
2003-05-08 07:40:22.08 server Server Process ID is 1980.
2003-05-08 07:40:22.08 server Logging SQL Server messages in file 'D:\MSSQL\log\ERRORLOG'.
2003-05-08 07:40:22.10 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2003-05-08 07:40:22.39 server SQL Server configured for thread mode processing.
2003-05-08 07:40:22.41 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-05-08 07:40:22.47 server Attempting to initialize Distributed Transaction Coordinator.
2003-05-08 07:40:24.92 spid2 Starting up database 'master'.
2003-05-08 07:40:25.35 server Using 'SSNETLIB.DLL' version '8.0.760'.
2003-05-08 07:40:25.35 spid5 Starting up database 'model'.
2003-05-08 07:40:25.38 spid2 Server name is 'OURSERVER'.
2003-05-08 07:40:25.38 spid8 Starting up database 'msdb'.
2003-05-08 07:40:25.38 spid9 Starting up database 'ZZZ_ONT'.
2003-05-08 07:40:25.41 spid10 Starting up database 'ZZZ_TST'.
2003-05-08 07:40:25.42 spid11 Starting up database 'ZZZ_PILOT'.
2003-05-08 07:40:25.42 spid12 Starting up database 'ZZZ_TMP'.
2003-05-08 07:40:25.44 spid13 Starting up database 'ZZZ_ONT_SR'.
2003-05-08 07:40:25.44 spid14 Starting up database 'ZZZ_ONT_FR'.
2003-05-08 07:40:25.46 spid15 Starting up database 'SRV0000log'.
2003-05-08 07:40:25.61 server SQL server listening on 999.999.999.999: 9999.
2003-05-08 07:40:25.61 server SQL server listening on 999.999.999.999: 9999.
2003-05-08 07:40:25.61 server SQL server listening on 999.999.999.999: 9999.
2003-05-08 07:40:25.75 spid14 Analysis of database 'ZZZ_ONT_SR' (10) is 100% complete (approximately 0 more seconds)
2003-05-08 07:40:25.81 spid12 Analysis of database 'ZZZ_TMP' (8) is 100% complete (approximately 0 more seconds)
2003-05-08 07:40:25.88 spid13 Analysis of database 'ZZZ_ONT_FR' (9) is 100% complete (approximately 0 more seconds)
2003-05-08 07:40:25.94 spid5 Clearing tempdb database.
2003-05-08 07:40:26.00 spid13 Starting up database 'SRV0099log'.
2003-05-08 07:40:26.11 spid14 Starting up database 'EuroPC_TST'.
2003-05-08 07:40:26.22 spid8 Starting up database 'ZZZ_ACC'.
2003-05-08 07:40:26.30 spid15 Starting up database 'ZZZ_PRD_FFF_bid'.
2003-05-08 07:40:26.31 spid10 Starting up database 'POD_ONT_DB'.
2003-05-08 07:40:26.41 spid12 Starting up database 'ATT_ONT'.
2003-05-08 07:40:26.44 spid9 Starting up database 'ZZZ_ONT_W2K'.
2003-05-08 07:40:28.55 server SQL server listening on TCP, Shared Memory, Named Pipes.
2003-05-08 07:40:28.55 server SQL Server is ready for client connections
2003-05-08 07:40:28.71 spid5 Starting up database 'tempdb'.
2003-05-08 07:40:29.46 spid15 Analysis of database 'ZZZ_PRD_FFF_bid' (19) is 100% complete (approximately 0 more seconds)
2003-05-08 07:40:30.28 spid2 Recovery complete.
2003-05-08 07:40:30.28 spid2 SQL global counter collection task is created.
2003-05-08 07:41:04.05 spid51 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
2003-05-08 07:41:12.50 spid52 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'.
May 13, 2003 at 6:28 am
Based on this line
2003-05-08 07:40:30.28 spid2 Recovery complete.
I would have to say this SQL Server was stopped (either just service or whole box).
If those DB are highly accessed and had users in them at the time of the stop with objects open or an exception was thrown before the stop and these items were open at the time.
I suspect but cannot confirm it is just integrity checks that SQL is performing against objects that could based on the reason for the stop have become suspect.
Unfortunately I don't have any specific way to test here other than slap my local server own but not sure what event might trigger that to occurr.
Do you have other logs of this happening and if so do you see the recovery complete message shortly after those?
May 13, 2003 at 7:06 am
Yes, SQLserver was stopped - something which does not happen often and the logs are cycled every day and I therefor do not have any other logs to compare this with and also no other 2K servers to play stopping-and-starting with. I also do not expect this to be serious, but just like knowing why things happen. I'll keep an eye on this and see what happens next time.
May 13, 2003 at 7:48 am
If I come across anything else I will pass along.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply