Wierd Error Log Messages/behavior

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2008 Forums

SQL Server Administration (2008)

Wierd Error Log Messages/behavior

Author

Topic

TonyTheDBA
Posting Yak Master

121 Posts

Posted - 2010-11-11 : 02:50:05

Doh! Wrong Forum Sorry this should be in the SQL 2000 Admin

For a while now, I have had a SQL Server behaving rather oddly. Every now and again one of the databases just goes off line or is Unavailable . . . but this has now started to happen more frequently and rather than being the test DB it has started happening on the Live DB (Yeah I know live and test on the same server . . . don't ask)

Having finally got some time to investigate (Restarting the SQL Server service brings it back on line) The Error log shows some strange SQL Server behavior . . . This is the Head of the log, but it continues like this all day . . . Users have no issues getting in.

I suspect that I should do a CHECKDB etc, or possibly dump the database into a new one . . . or backup and restore the database . . . but I've never seen anything like this before . . . Any ideas?

Oh and we are planning an upgrade to SQL 2008 for this application in the near future so it may or may not become an issue.

Thanks Gurus

2010-11-11 07:36:08.99 server    Microsoft SQL Server  2000 - 8.00.2282 (Intel X86) 
	Dec 30 2008 02:22:41 
	Copyright (c) 1988-2003 Microsoft Corporation
	Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

2010-11-11 07:36:08.99 server    Copyright (C) 1988-2002 Microsoft Corporation.
2010-11-11 07:36:08.99 server    All rights reserved.
2010-11-11 07:36:08.99 server    Server Process ID is 1608.
2010-11-11 07:36:08.99 server    Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2010-11-11 07:36:09.00 server    SQL Server is starting at priority class 'high'(2 CPUs detected).
2010-11-11 07:36:09.24 server    SQL Server configured for thread mode processing.
2010-11-11 07:36:09.24 server    Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2010-11-11 07:36:09.55 server    Attempting to initialize Distributed Transaction Coordinator.
2010-11-11 07:36:12.55 spid3     Starting up database 'master'.
2010-11-11 07:36:12.72 spid3     Server name is 'BBCSPOC'.
2010-11-11 07:36:12.72 spid3     Skipping startup of clean database id 7
2010-11-11 07:36:12.72 spid3     Skipping startup of clean database id 8
2010-11-11 07:36:12.72 spid3     Skipping startup of clean database id 10
2010-11-11 07:36:12.72 spid3     Skipping startup of clean database id 11
2010-11-11 07:36:12.86 spid5     Starting up database 'model'.
2010-11-11 07:36:12.86 spid6     Starting up database 'msdb'.
2010-11-11 07:36:12.86 server    Using 'SSNETLIB.DLL' version '8.0.2039'.
2010-11-11 07:36:12.86 spid9     Starting up database 'SQLAudit'.
2010-11-11 07:36:12.86 spid10    Starting up database 'QuestWorkDatabase'.
2010-11-11 07:36:12.86 spid11    Starting up database 'BBCADMIN'.
2010-11-11 07:36:12.92 spid11    Analysis of database 'BBCADMIN' (9) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:13.11 spid5     Clearing tempdb database.
2010-11-11 07:36:13.45 server    SQL server listening on 10.2.1.162: 1433.
2010-11-11 07:36:13.45 server    SQL server listening on 127.0.0.1: 1433.
2010-11-11 07:36:13.92 spid5     Starting up database 'tempdb'.
2010-11-11 07:36:13.95 spid3     Recovery complete.
2010-11-11 07:36:13.95 spid3     SQL global counter collection task is created.
2010-11-11 07:36:14.95 server    SQL server listening on TCP, Shared Memory, Named Pipes.
2010-11-11 07:36:14.95 server    SQL Server is ready for client connections
2010-11-11 07:36:16.41 spid9     Starting up database 'SPOCCTest'.
2010-11-11 07:36:16.42 spid9     Analysis of database 'SPOCCTest' (8) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:18.59 spid51    Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure 'xp_msver'.
2010-11-11 07:36:20.19 spid51    Using 'xpstar.dll' version '2000.80.2282' to execute extended stored procedure 'xp_regread'.
2010-11-11 07:36:20.72 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:21.02 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:21.16 spid51    Starting up database 'SPOCCLive_Backup4March2008'.
2010-11-11 07:36:21.28 spid51    Analysis of database 'SPOCCLive_Backup4March2008' (11) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:21.47 spid51    Starting up database 'SPOCCLive_Backup4March2008'.
2010-11-11 07:36:21.48 spid51    Analysis of database 'SPOCCLive_Backup4March2008' (11) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:21.64 spid51    Starting up database 'SPOCCLive_ReadyToExport'.
2010-11-11 07:36:21.86 spid51    Starting up database 'SPOCCLive_ReadyToExport'.
2010-11-11 07:36:22.03 spid51    Starting up database 'SPOCCTest'.
2010-11-11 07:36:22.03 spid51    Analysis of database 'SPOCCTest' (8) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:22.08 spid51    Starting up database 'SPOCCTest'.
2010-11-11 07:36:22.08 spid51    Analysis of database 'SPOCCTest' (8) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:22.25 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:22.45 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:22.64 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:22.77 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:22.97 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:23.05 spid51    Starting up database 'SPOCCLive_Backup4March2008'.
2010-11-11 07:36:23.09 spid51    Analysis of database 'SPOCCLive_Backup4March2008' (11) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:23.23 spid51    Starting up database 'SPOCCLive_Backup4March2008'.
2010-11-11 07:36:23.25 spid51    Analysis of database 'SPOCCLive_Backup4March2008' (11) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:23.38 spid51    Starting up database 'SPOCCLive_Backup4March2008'.
2010-11-11 07:36:23.39 spid51    Analysis of database 'SPOCCLive_Backup4March2008' (11) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:23.50 spid51    Starting up database 'SPOCCLive_Backup4March2008'.
2010-11-11 07:36:23.52 spid51    Analysis of database 'SPOCCLive_Backup4March2008' (11) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:23.61 spid51    Starting up database 'SPOCCLive_Backup4March2008'.
2010-11-11 07:36:23.63 spid51    Analysis of database 'SPOCCLive_Backup4March2008' (11) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:23.66 spid51    Starting up database 'SPOCCLive_ReadyToExport'.
2010-11-11 07:36:23.94 spid51    Starting up database 'SPOCCLive_ReadyToExport'.
2010-11-11 07:36:24.03 spid12    Starting up database 'SPOCCLive'.
2010-11-11 07:36:24.16 spid51    Starting up database 'SPOCCLive_ReadyToExport'.
2010-11-11 07:36:24.49 spid51    Starting up database 'SPOCCLive_ReadyToExport'.
2010-11-11 07:36:24.70 spid51    Starting up database 'SPOCCLive_ReadyToExport'.
2010-11-11 07:36:24.78 spid51    Starting up database 'SPOCCTest'.
2010-11-11 07:36:24.78 spid51    Analysis of database 'SPOCCTest' (8) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:24.83 spid51    Starting up database 'SPOCCTest'.
2010-11-11 07:36:24.83 spid51    Analysis of database 'SPOCCTest' (8) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:24.88 spid51    Starting up database 'SPOCCTest'.
2010-11-11 07:36:24.89 spid51    Analysis of database 'SPOCCTest' (8) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:24.92 spid51    Starting up database 'SPOCCTest'.
2010-11-11 07:36:24.94 spid51    Analysis of database 'SPOCCTest' (8) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:24.99 spid51    Starting up database 'SPOCCTest'.
2010-11-11 07:36:24.99 spid51    Analysis of database 'SPOCCTest' (8) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:25.22 spid12    Starting up database 'SPOCCLive'.
2010-11-11 07:36:25.44 spid9     Starting up database 'SPOCCLive'.
2010-11-11 07:36:25.64 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:26.41 spid12    Starting up database 'SPOCCLive'.
2010-11-11 07:36:26.56 spid9     Starting up database 'SPOCCLive'.
2010-11-11 07:36:27.24 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:27.36 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:27.50 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:27.63 spid12    Starting up database 'SPOCCLive_Backup4March2008'.
2010-11-11 07:36:27.63 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:27.67 spid12    Analysis of database 'SPOCCLive_Backup4March2008' (11) is 100% complete (approximately 0 more seconds)
2010-11-11 07:36:28.06 spid51    Starting up database 'SPOCCLive'.
2010-11-11 07:36:28.19 spid51    Starting up database 'SPOCCLive'.

--
Regards
Tony The DBA

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-11-11 : 06:00:39

Your databases are likely set to autoclose. Disable that setting.

--
Gail Shaw
SQL Server MVP

TonyTheDBA
Posting Yak Master

121 Posts

Posted - 2010-11-11 : 08:36:13

quote:
Originally posted by GilaMonster

Your databases are likely set to autoclose. Disable that setting.

Gail,

Absolutely spot on! Thank you . . . I'm now off to shoot the supplier that changed the settings when they last did a 'Health Check' . . . If it wasn't for the fact that they use the same account as the application (I know . . . but hey some of our suppliers still use the sa account and hard code it into their software!!!!!!!!

) and it is a sysadmin, I'd disable the account.

"Hit any User/supplier to continue"

--
Regards
Tony The DBA

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources