February 6, 2015 at 10:30 am
The other morning an automated Integrity Check job produced the following message:
DBCC CHECKDB (DBName) executed by TBECU\sqlservice found 2 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 11 seconds. Internal database snapshot has split point LSN = 0000f4c3:00005bec:0001 and first LSN = 0000f4c3:00005beb:0001.
This is all the information I have on this. I ran DBCC CHECKDB manually the following day on this database and it came up clean. I learned from researching this that the "LSN =" part is simply the point at which the CHECKDB snapshot was created. Were the two errors random glitches, or minor corruption that was corrected by some other process before I ran CHECKDB the second time?
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy