How to open a 12GB SQL error log file without shrinking it

Question

Post reply

How to open a 12GB SQL error log file without shrinking it

ssaffar55

SSC Enthusiast

Points: 129
More actions
September 12, 2016 at 10:16 pm

#313221

Hi Team,
Is there a way of opening this log file to review it or is it as good as gone at 12GB.
I was hoping to see when the errors started etc.
Any advice would be great.
Ta
September 12, 2016 at 11:33 pm

This was removed by the editor as SPAM

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

What kind of log file are you talking about?

An error log? If so, something like Notepad++ will be able to open it.

A transaction log? If so, there are no errors in a transaction log to read.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Sue_H SSC Guru Points: 90860 More actions · Answer 2

If it's the error log and not a log file and you want to read through it, it might be easier or faster (depending) to use xp_readerrorlog and filter it by times, walk through reading it that way. Or filter it by keywords - error, failed. It comes in handy for large error logs.

Sue

Gazareth One Orange Chip Points: 27737 More actions · Answer 3

You can also use the Get-Content cmdlet in powershell to read out just a set number of lines from the start or end rather than the whole file.

Eric M Russell SSC Guru Points: 125561 More actions · Answer 4

How did you end with a 12 GB mssql ERRORLOG file, if that's what you're talking about?

Anyhow, there are some Hex editors like HxD or XVI32 that can browse and search files in raw mode, one page at a time, rather than loading the entire file into memory. HxD can other neat stuff like browse process space for executables in memory.

https://www.mh-nexus.de/en/

http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm

But perhaps the best thing to do is load this file into a table using SSMS Import Wizard.

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

ChrisTaylor SSCarpal Tunnel Points: 4527 More actions · Answer 5

If indeed it is an errorlog and not a tlog file you are trying to open then I'm old skool and still love PFE32 for large files

_________________________________________________________________________________SQLGeordieWeb:- Jarrin ConsultancyBlog:- www.chrisjarrintaylor.co.ukTwitter:- @SQLGeordie