Hey Tom, That just sounds like the PRINT statement is messing up the size of the string. Two thoughts without seeing it:
* LEFT on the thing being printed * Try the option on the Advanced tab for the job (or job step – can’t remember which) that lets you put the whole message in, not just the short form of the message. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.sqldownunder.com%2F&data=02%7C01%7Csspahelp%40microsoft.com%7C1f0ea4d6b97e4d897f3708d666d1e890%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636809449091516274&sdata=SLHeEGAMmWUY5YIwcC4oAPYr%2F9RIZdi4MNASsdzwX2I%3D&reserved=0> |http://greglow.me<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgreglow.me%2F&data=02%7C01%7Csspahelp%40microsoft.com%7C1f0ea4d6b97e4d897f3708d666d1e890%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636809449091526278&sdata=IU8tnAITCjBxWafi3A9XpO9lF3PIwZJ8ad3t36lnxvs%3D&reserved=0> From: ozdotnet-boun...@ozdotnet.com <ozdotnet-boun...@ozdotnet.com> On Behalf Of Tom P Sent: Friday, 27 November 2020 12:05 PM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: [OT] SQL Server job failures when "printing" too much? Hi folks - Greg Low in particular :-) I have a SQL Server agent job that is failing with error "String data, right truncation [SQLSTATE 01004]". It seems the reason for this is the stored procedure the job calls has a bunch of PRINT statements which I understand find their way through to the job history output window in SSMS. If I remove the PRINT statements the error goes away. Google hasn't helped me much, any SQL Server pros here that have any ideas how to address this? Thanks Tom
