THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Greg Low (The Bit Bucket: IDisposable)

Ramblings of Greg Low (SQL Server MVP, MCM and Microsoft RD) - SQL Down Under

Avoiding invalid object name errors with temporary tables for BizTalk, Reporting Services and apps using SET FMTONLY

Published Tuesday, April 11, 2017 2:26 PM by Greg Low

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Greg O'Connell said:

Nice article as always Greg. For some context, and  to give the punters an idea of the high esteem (not) in which SET FMTONLY is now held, even at Microsoft, BOL says:

"...Note

Do not use this feature. This feature has been replaced by sp_describe_first_result_set (Transact-SQL), sp_describe_undeclared_parameters (Transact-SQL), sys.dm_exec_describe_first_result_set (Transact-SQL), and sys.dm_exec_describe_first_result_set_for_object (Transact-SQL)...." (https://docs.microsoft.com/en-us/sql/t-sql/statements/set-fmtonly-transact-sql)

I'm amused that they still describe it as a "feature"; I yearn for the day that it is finally banished from the SQL Server ecosystem forever. :-)

Thanks again.

April 23, 2017 4:21 AM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

Tags

No tags have been created or used yet.

Archives

Privacy Statement