This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 7.000000000000001%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Hello,
We have migrated some systems to SQL2019, I was cheking one system and found the SQL Server Error log #2 is empty.. it doesnt have any information..
Any idea ?
Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 30%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
Perhaps you didn't re-start your SQL Server since the migration enough times to get to #2? Or are you saying that the others (#3, #4, etc) aren't empty. Also, is #2 completely empty, or is there some text in there?
Hi
No it is restarted couple of time..
But i noticed the SQL Server Error Log#2 is empty, it is completely empty..
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 46%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Hi @Biltz ,
It seems the archive error log #1 is empty too.
Could you please check if errorlog.1 and errorlog.2 in C:\Program Files\Microsoft SQL Server\MSSQL15.\MSSQL\Log is empty?
Is there any information in the current error log?
Best Regards,
Amelia
Any help on this?
I don't know what might have happened. But I have a counter-question: do you have any real concern? If everything is working normally, I can't see why this is a problem?
You could check Windows event log to see if there are any messages around the timestamp for this file.
I agree with Erland. Except for doing forensics by reading the event viewer during this time period, we can't say why this happened. Personally, I wouldn't bother.
As an aside, I would use File Explorer instead of sp_readerrorlog to check the files and open each file in an editor. Just to be 100% certain that it isn't anything strange connected with sp_readerrorlog.