Avoiding invalid object name errors with temporary tables for BizTalk, Reporting Services and apps using SET FMTONLY
When applications need to call stored procedures, they try to work out what the returned data will look like ie: which columns come back, what data types are they, etc.
The old way of doing this was to call SET FMTONLY ON. Unfortunately, many applications like Biztalk and versions of Reporting Services still did this, and/or still do this. The same issue happens with LINQ to SQL and other tools that use SQL Metal.
2017-04-11