<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www2.sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Connect Item: Globally-Scoped Metadata Views</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/2009/04/16/connect-item-globally-scoped-metadata-views.aspx</link><description>Ever tried writing a more or less database-agnostic administrative script? If the experience didn't make your head spin, you either have a stronger constitution than most DBAs or your script doesn't actually work properly. The fact is, due to the way</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: Connect Item: Globally-Scoped Metadata Views</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/2009/04/16/connect-item-globally-scoped-metadata-views.aspx#13330</link><pubDate>Thu, 16 Apr 2009 15:21:08 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:13330</guid><dc:creator>Alexander Kuznetsov</dc:creator><description>&lt;p&gt;Great suggestion!&lt;/p&gt;
</description></item><item><title>re: Connect Item: Globally-Scoped Metadata Views</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/2009/04/16/connect-item-globally-scoped-metadata-views.aspx#13332</link><pubDate>Thu, 16 Apr 2009 16:40:38 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:13332</guid><dc:creator>Michelle Ufford</dc:creator><description>&lt;p&gt;Voted, 5 stars!&lt;/p&gt;
</description></item><item><title>re: Connect Item: Globally-Scoped Metadata Views</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/2009/04/16/connect-item-globally-scoped-metadata-views.aspx#13334</link><pubDate>Thu, 16 Apr 2009 18:11:52 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:13334</guid><dc:creator>Ranga Narasimhan</dc:creator><description>&lt;p&gt;Great Idea. voted 5 stars.&lt;/p&gt;
</description></item><item><title>re: Connect Item: Globally-Scoped Metadata Views</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/2009/04/16/connect-item-globally-scoped-metadata-views.aspx#13350</link><pubDate>Sat, 18 Apr 2009 14:21:09 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:13350</guid><dc:creator>Saggi Neumann</dc:creator><description>&lt;p&gt;Voted.&lt;/p&gt;
&lt;p&gt;It reminded me of another annoyance - index_id, used with and returned from sys.dm_db_index_physical_stats. Why aren't there index_name()/index_id() functions that can also take a database_id parameter, with ALTER INDEX the &amp;quot;right way&amp;quot; to rebuild/reorganize indexes? &lt;/p&gt;
</description></item></channel></rss>