Getting the Full Logging Message in SQL Server …

I needed to help a customer today to read some SQL Server Job History messages, but we were getting that awful 1024 truncation going on.  Happily there is a great fix for this here on SQL Server Central.  Basically you have to tell SQL Server to log to a table in msdb, then the full details are available.  There’s a sneaky bit of SQL to get the meaningful stuff out, I won’t spoil the original author’s thunder by posting it here.  Check out the solution for yourself.  Oh you need to register with SQL Server Central to get the full article.  FYI, the author of this blog post has NO affiliation with SQL Server Central. It’s just a great resource…


Dave Mc

About davemcmahon81
Software Developer & Architect, User Group Leader, Speaker, Writer, Blogger, Occasional Guitarist, Man-made Global Warming Sceptic, Climate Change Believer, General Optimist but most of all proud Husband and Dad ...

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: