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…

Cheers

Dave Mc