If you call yourself SQL Server DBA, then you
must be able to interpret SQL Server Log, One of a common information message
captured by SQL Server Log is
This instance of
SQL Server has been using a process ID of 2308 since 5/3/2012 2:30:52 AM
(local) 5/3/2012 6:30:52 AM (UTC). This is an informational message only; no
user action is required.(process id and time would be different every time)
First thing to note about this log entry is that it’s just an information message and no user action is required. Mean NO NEED TO WORRY. This is just an information message that SQL Server instance using a process id (in my case it is 2308), since SQL Server services are started (in my case SQL Server services are started at 5/3/2012 2:30:52 AM) and after a month instance is still running.
SQL Server creates a log entry for this message on each date change. So you can find one entry for each 24 hours.
To verify this process id, open Task Manager and move to “Processes” tab, click on “View” in menu, “Select Columns”. Select PID (Process Identifier). Now it will start showing process identifier for each process. Check process identifier for sqlserver.exe
------------------------------------------------------------------------------------
Read More
about SQL Server Log Errors/Messages
- SQL Server has encountered 1 occurrence(s) of cachestore flush
- DeviceIoControl failed, error 21
- SQL Server has encountered occurrence(s) of I/O requests taking longer than 15 seconds to complete
- The time stamp counter of CPU on scheduler id 13 is not synchronized with other CPUs.
- I/O is frozen on database DatabaseName
Thanks for the info, that was helpful. I was a bit worried why I was getting those SQL logs.
ReplyDelete