Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Does we should worry about informational message in error logs? Expand / Collapse
Author
Message
Posted Thursday, October 7, 2010 7:36 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, October 27, 2014 6:12 AM
Points: 237, Visits: 901
Hi,

SQL Server Logs some Informational messages in error log. I have found like "This instance of SQL Server has been using a process ID of 1588 since datetime"

Does we should be worry about informational message in error logs. Can some one help me to understand why SQL server informs us to using process id from long time. should I take action as DBA?

Some Informational messages are understandable but some are not. Is there a detail on internet or on Microsoft sites to understand them?


Ram
MSSQL DBA
Post #1000467
Posted Thursday, October 7, 2010 8:02 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Tuesday, January 28, 2014 8:15 AM
Points: 3,065, Visits: 4,639
Reo (10/7/2010)
SQL Server Logs some Informational messages in error log. I have found like "This instance of SQL Server has been using a process ID of 1588 since datetime"

Does we should be worry about informational message in error logs. Can some one help me to understand why SQL server informs us to using process id from long time. should I take action as DBA?

Some Informational messages are understandable but some are not. Is there a detail on internet or on Microsoft sites to understand them?


I see informational messages in error logs as events SQL Server wants you to be aware of, not necessarily worried about them.

Having spare time I would check informational messages and investigate further the ones that call my attention.

SQL Server KB is plenty of information to help understand such messages.


_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Post #1000506
Posted Thursday, October 7, 2010 9:11 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 10:22 AM
Points: 31,214, Visits: 15,658
I tend not to worry about most of them. You could have processes that are connected for a long time, so I wouldn't worry about that. I think that's left over from when we had fewer resources and worried about stalled/stuck connections.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1000606
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse