December 14, 2009 at 9:19 am
SQLAGENT$SQLSERVERVIEW is The SQL Agent Service that controls your SQL Jobs. Since your 3rd party app relies on some jobs to keep DB trimmed and cleaned out, you should make sure that service is restarted as part of your checklist when the server reboots. You might be able to find something in the eventlog as to why it didn't start the last time.
Yes, you should probably keep those jobs running - they are a part of the app you bought. They would better be able to tell you if you will need them in your environment or not.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 14, 2009 at 7:58 pm
CirquedeSQLeil (12/14/2009)
SQLAGENT$SQLSERVERVIEW is The SQL Agent Service that controls your SQL Jobs. Since your 3rd party app relies on some jobs to keep DB trimmed and cleaned out, you should make sure that service is restarted as part of your checklist when the server reboots. You might be able to find something in the eventlog as to why it didn't start the last time.Yes, you should probably keep those jobs running - they are a part of the app you bought. They would better be able to tell you if you will need them in your environment or not.
Thanks for your experience indeed. I suspect there's some 3rd party app that make conflicts with SQLAGENT$SQLSERVERVIEW service and make this service cannot start. BTW we'll start this service manually in production and see that ServerViewDB.log can be trimmed down or not.
Thanks and regards,
Wallace
December 14, 2009 at 9:15 pm
You're welcome.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 14, 2009 at 11:16 pm
BTW, I grep the error log whenever fail to start SQLAGENT$SQLSERVERVIEW service when reboot server:
Agent Log:
2009-12-15 13:00:07 - ! [241] Startup error: Unable to initialize error reporting system (reason: The EventLog service has not been started)
2009-12-15 13:01:36 - ? [098] SQLServerAgent terminated (normally)
Error Log:
2009-12-15 13:00:05.65 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 1)
2009-12-15 13:00:05.65 server Copyright (C) 1988-2002 Microsoft Corporation.
2009-12-15 13:00:05.65 server All rights reserved.
2009-12-15 13:00:05.65 server Server Process ID is 3572.
2009-12-15 13:00:05.65 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$SQLSERVERVIEW\LOG\ERRORLOG'.
2009-12-15 13:00:05.65 server SQL Server is starting at priority class 'normal'(4 CPUs detected).
2009-12-15 13:00:05.89 server SQL Server configured for thread mode processing.
2009-12-15 13:00:05.89 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2009-12-15 13:00:05.96 spid3 Starting up database 'master'.
2009-12-15 13:00:06.07 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2009-12-15 13:00:06.07 spid5 Starting up database 'model'.
2009-12-15 13:00:06.09 spid3 Server name is 'SITNACCDB61\SQLSERVERVIEW'.
2009-12-15 13:00:06.10 spid8 Starting up database 'msdb'.
2009-12-15 13:00:06.10 spid9 Starting up database 'ServerViewDB'.
2009-12-15 13:00:06.17 spid5 Clearing tempdb database.
2009-12-15 13:00:06.28 spid8 Recovery is checkpointing database 'msdb' (4)
2009-12-15 13:00:06.45 server SQL server listening on 10.26.30.82: 1160.
2009-12-15 13:00:06.45 server SQL server listening on 127.0.0.1: 1160.
2009-12-15 13:00:06.51 server SQL server listening on TCP, Shared Memory, Named Pipes.
2009-12-15 13:00:06.51 server SQL Server is ready for client connections
2009-12-15 13:00:06.65 spid5 Starting up database 'tempdb'.
2009-12-15 13:00:06.81 spid3 Recovery complete.
2009-12-15 13:00:06.81 spid3 SQL global counter collection task is created.
2009-12-15 13:07:49.91 spid54 Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'.
2009-12-15 13:30:00.86 spid56 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'xp_instance_regread'.
2009-12-15 13:45:00.50 backup Log backed up: Database: ServerViewDB, creation date(time): 2009/12/14(14:36:33), first LSN: 423:231:1, last LSN: 423:242:1, number of dump devices: 1, device information: (FILE=26, TYPE=DISK, MEDIANAME='ServerViewDB': {'ServerViewDBLog'}).
I have observed application and system event from event viewer but no reason to state why that service cannot be started. On the other hand, we have manually turned off the SQL 2005 analysis service and reporting service. Do the above two services necessary for starting up
SQLAGENT$SQLSERVERVIEW service?(But even we turn on the above two services the SQLAGENT$SQLSERVERVIEW service cannot be started in our UAT environment). Any suggestions on how to find out the reason why SQLAGENT$SQLSERVERVIEW service cannot start? Thanks a lot.
Best regards,
Wallace
December 14, 2009 at 11:53 pm
BTW, are these MSSQL$SQLSERVERVIEW and SQLAGENT$SQLSERVERVIEW services belongs to SQL Server 2005 Enterprise Edition products, or other 3rd party application products? Thanks a lot.
Thanks and regards,
Wallace
December 15, 2009 at 9:12 am
Anything that is Serverview is not a MS SQL product. They are 3rd party apps being installed into SQL server. As for the service names with Serverview in them - that is a named instance that somebody used for this 3rd party app.
The version of SQL that you are running for this Serverview Instance is actually SQL 2000 and not SQL 2005 - according to your event log.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 15, 2009 at 7:28 pm
CirquedeSQLeil (12/15/2009)
Anything that is Serverview is not a MS SQL product. They are 3rd party apps being installed into SQL server. As for the service names with Serverview in them - that is a named instance that somebody used for this 3rd party app.The version of SQL that you are running for this Serverview Instance is actually SQL 2000 and not SQL 2005 - according to your event log.
Previously I misunderstand that this SQLSERVERVIEW is SQL Server product but actually it's our 3rd party product. Hence I have asked too many questions unrelated to you and Microsoft SQL Server and sorry about that :P. Thank you for your opinion and we'll ask our vendor about this SQLSERVERVIEW and ServerViewDB problem. Thanks a lot.
Best regards,
Wallace
December 15, 2009 at 7:33 pm
NP - you're welcome.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 8 posts - 16 through 22 (of 22 total)
You must be logged in to reply to this topic. Login to reply