If you’re like me, you like using descriptive variable, procedure and function names. Along with those, descriptive transaction names are great, so you know exactly what type of havoc you were throwing at SQL Server. But, if you’re too descriptive, you’ll get the following error:

Msg 103, Level 15, State 2, Line 1
The identifier that starts with 'MyReallyLongTransactionNameBecauseLongNamesAreCool' is too long. Maximum length is 32.

Not cool, especially if you’re using dynamic SQL to create automated scripts. In this case, simply change the transaction identifier to something a little smaller, but just as descriptive.


Rudy Rodarte is a SQL Server Database professional based in Austin, TX. Over his career, Rudy has worked with SSRS, SSIS, performance tuning troubleshooting. When away from Keyboard, Rudy goes to Spurs and Baylor Bear sporting events.

More Posts - Website - Twitter