Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

← SQL Server

Traceflag 460 causing truncation errors on code paths that are not followed

This is an odd one. I have tested this on both SQL Server 2017 CU12 and CU13 (in a container and on my production boxes).

If you have an IF/ELSE condition, and you are inserting into a table variable in the ELSE, and that INSERT would cause a truncation issue, it will throw an error, EVEN IF THE CODE IS NOT EXECUTED.

I have attached a reprop script that creates a database called "Repro" and runs the code. When TF460 is enabled, the ELSE block with throw an error when inserting into a table variable, even though it is impossible to even get to the ELSE block, since the IF logic is "IF ( 1= 1)". If you convert the code to a temp table the error goes away, and if you disable TF460 the error goes away.

21 votes
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Mark Wilkinson shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

5 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Close
Close
Submitting...

SQL Server: Bugs

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice