September 14, 2017 at 7:29 am
We just made the jump from SQL Server 2008 to 2014, and as a result I am now using SSMS 2014. I tried SSMS 17 but did not care for the interface style. I have noticed some really annoying differences in the way that the Object Explorer script generator behaves in 2014 vs 2008 and was wondering if there is any way to get back the functionality lost?
For example, with a DROP and CREATE, the script generator no longer includes the IF EXISTS statement on the DROP. This was incredibly useful to me when generating scripts to create work files in SSIS packages. I have found the option in 2014 to "Check for object existence", and it includes both a check on the DROP and the CREATE, but this then changes the behavior of MODIFY on a Stored Procedure so that it displays as a "dynamic" scripting format. (using a EXEC dbo.sp_executesql @statement = '...)
I have also noticed that the script generator for SELECT no longer includes the database name. The only work around for this that I have found is to set the SELECT Top N to 0, which selects all records, and does include the database name in the script.
These tiny changes and incredibly annoying to me.
Does anyone have any suggestions, other that "deal with it"?
PK
September 14, 2017 at 7:42 am
Check out Tools/Options/SQL Server Object Explorer/Scripting
You can change the behaviour there (eg, check for object existence). If, after checking that, you still have questions, please post back.
September 14, 2017 at 8:24 am
I have found the option in 2014 to "Check for object existence", and it includes both a check on the DROP and the CREATE, but this then changes the behavior of MODIFY on a Stored Procedure so that it displays as a "dynamic" scripting format. (using a EXEC dbo.sp_executesql @statement = '...)
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply