Search results matching tags 'Management Studio' and 'sp_MSforeachdb'http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&tag=Management+Studio,sp_MSforeachdb&orTags=0Search results matching tags 'Management Studio' and 'sp_MSforeachdb'en-USCommunityServer 2.1 SP2 (Build: 61129.1)Connect Digest : 2012-07-06http://sqlblog.com/blogs/aaron_bertrand/archive/2012/07/06/connect-digest-2012-07-06.aspxFri, 06 Jul 2012 14:37:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:44218AaronBertrand<p>I've filed a few Connect items recently that I think are important.</p>
<hr><p>In <a href=http://connect.microsoft.com/SQLServer/feedback/details/752210/doc-ddl-trigger-topic-suggests-that-rollbacks-run-before-action target=_blank>#752210</a>, I complain that the documentation for DDL triggers suggests that they can prevent certain DDL from being run, which is not the case at all.&nbsp;</p><p>&nbsp; &nbsp; <a href=http://connect.microsoft.com/SQLServer/feedback/details/752210/doc-ddl-trigger-topic-suggests-that-rollbacks-run-before-action target=_blank>http://connect.microsoft.com/SQLServer/feedback/details/752210/doc-ddl-trigger-topic-suggests-that-rollbacks-run-before-action</a></p>
<hr>
<p>In <a target=_blank href=http://connect.microsoft.com/SQLServer/feedback/details/745796/ssms-generate-scripts-for-data-scripts-datetime-as-binary>#745796</a>, I complain that scripting datetime data in Management Studio yields output that contains a binary representation instead of a human-readable string. I suspect this is to avoid ambiguity but I guess someone forgot that there are unambiguous formats available (*cough* YYYYMMDD *cough*). &nbsp;</p><p>&nbsp; &nbsp; <a target=_blank href=http://connect.microsoft.com/SQLServer/feedback/details/745796/ssms-generate-scripts-for-data-scripts-datetime-as-binary>http://connect.microsoft.com/SQLServer/feedback/details/745796/ssms-generate-scripts-for-data-scripts-datetime-as-binary</a></p>
<hr>
<p>In <a href=http://connect.microsoft.com/SQLServer/feedback/details/752629/disable-sp-msforeachdb-by-default-or-fix-it target=_blank>#752629</a>, I complain about the broken procedure sp_msforeachdb, which I've <a target=_blank href=http://sqlblog.com/blogs/aaron_bertrand/archive/2010/02/08/bad-habits-to-kick-relying-on-undocumented-behavior.aspx>complained about</a> <a target=_blank href=http://sqlblog.com/blogs/aaron_bertrand/archive/2010/12/29/a-more-reliable-and-more-flexible-sp-msforeachdb.aspx>many times before</a> and have even <a target=_blank href=http://www.mssqltips.com/sqlservertip/2201/making-a-more-reliable-and-flexible-spmsforeachdb />written a more functional, alternative version that actually works</a>. I really think they need an ultimatum here: either fix the thing or turn it off by default. The only downside to turning it off by default: this will break maintenance plans that are probably breaking silently anyway.</p><p>&nbsp; &nbsp; <a href=http://connect.microsoft.com/SQLServer/feedback/details/752629/disable-sp-msforeachdb-by-default-or-fix-it target=_blank>http://connect.microsoft.com/SQLServer/feedback/details/752629/disable-sp-msforeachdb-by-default-or-fix-it</a></p>
&nbsp;<br>