<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"><channel><title>SQL Server Best Practices: Setting a Default Filegroup</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/05/21/sql-server-best-practices-setting-a-default-filegroup.aspx</link><description>When you create a database, you should always create Filegroups to store the data on multiple drives. Don't confuse this with just creating multiple files in a database - that is useful, but not the same. Let's take an example to explain what you want</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: SQL Server Best Practices: Setting a Default Filegroup</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/05/21/sql-server-best-practices-setting-a-default-filegroup.aspx#10066717</link><pubDate>Thu, 23 Sep 2010 13:43:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10066717</guid><dc:creator>BuckWoody</dc:creator><description>&lt;p&gt;Gustavo - Filegroups are at the database level.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10066717" width="1" height="1"&gt;</description></item><item><title>re: SQL Server Best Practices: Setting a Default Filegroup</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/05/21/sql-server-best-practices-setting-a-default-filegroup.aspx#10066680</link><pubDate>Thu, 23 Sep 2010 12:34:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10066680</guid><dc:creator>Gustavo Longo</dc:creator><description>&lt;p&gt;Hi Buck, is possible define a default filegroup in the server level? &lt;/p&gt;
&lt;p&gt;My idea is define a default filegroup before create to any database.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10066680" width="1" height="1"&gt;</description></item><item><title>re: SQL Server Best Practices: Setting a Default Filegroup</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/05/21/sql-server-best-practices-setting-a-default-filegroup.aspx#9791878</link><pubDate>Fri, 19 Jun 2009 21:56:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9791878</guid><dc:creator>BuckWoody</dc:creator><description>&lt;p&gt;Tom - you are correct. I always do it in a separate step so that I can pull it out for an ALTER statement on an existing system.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9791878" width="1" height="1"&gt;</description></item><item><title>re: SQL Server Best Practices: Setting a Default Filegroup</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/05/21/sql-server-best-practices-setting-a-default-filegroup.aspx#9791421</link><pubDate>Fri, 19 Jun 2009 21:01:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9791421</guid><dc:creator>Tom Groszko</dc:creator><description>&lt;p&gt;I don't understand why you describe an additional step is needed. The filegroup statement on the CREATE DATABASE command allows you to specify DEFAULT. What is accomplished by doing this in a seperate step?&lt;/p&gt;
&lt;p&gt;Tom&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9791421" width="1" height="1"&gt;</description></item><item><title>re: SQL Server Best Practices: Setting a Default Filegroup</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/05/21/sql-server-best-practices-setting-a-default-filegroup.aspx#9634399</link><pubDate>Fri, 22 May 2009 00:56:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9634399</guid><dc:creator>BuckWoody</dc:creator><description>&lt;p&gt;Mark, you are so correct. My original post had &amp;quot;master model and msdb&amp;quot; - but what I meant to say was &amp;quot;system tables&amp;quot;. The system databases are of course, well, databases, so they have their own filegroups!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9634399" width="1" height="1"&gt;</description></item><item><title>re: SQL Server Best Practices: Setting a Default Filegroup</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/05/21/sql-server-best-practices-setting-a-default-filegroup.aspx#9634381</link><pubDate>Fri, 22 May 2009 00:42:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9634381</guid><dc:creator>Mark Hions</dc:creator><description>&lt;p&gt;Buck may have post-TechEd flu. &amp;nbsp;The PRIMARY filegroup does *not* hold master, model, and msdb. &amp;nbsp;Those are system databases, and they contain PRIMARY filegroups of their own.&lt;/p&gt;
&lt;p&gt;I think he meant to say that the PRIMARY filegroup &amp;nbsp;holds the database metadata, aka system tables. &amp;nbsp;They are not accessible normally. &amp;nbsp;I agree with the recommendation to make another, non-PRIMARY filegroup become the default, however.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9634381" width="1" height="1"&gt;</description></item><item><title>re: SQL Server Best Practices: Setting a Default Filegroup</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/05/21/sql-server-best-practices-setting-a-default-filegroup.aspx#9633971</link><pubDate>Thu, 21 May 2009 19:32:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9633971</guid><dc:creator>johnw73</dc:creator><description>&lt;p&gt;Buck, could you clarify 'This is also the Filegroup that holds your master, msdb, tempdb and other objects.'? I have a feeling that this is the crux of your post, but when I read it, i infer that ANY filegroup named PRIMARY is shared, which I didn't expect.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9633971" width="1" height="1"&gt;</description></item><item><title>SQL Server Best Practices: Setting a Default Filegroup | Microsoft Share Point</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/05/21/sql-server-best-practices-setting-a-default-filegroup.aspx#9633779</link><pubDate>Thu, 21 May 2009 17:07:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9633779</guid><dc:creator>SQL Server Best Practices: Setting a Default Filegroup | Microsoft Share Point</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://microsoft-sharepoint.simplynetdev.com/sql-server-best-practices-setting-a-default-filegroup/"&gt;http://microsoft-sharepoint.simplynetdev.com/sql-server-best-practices-setting-a-default-filegroup/&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9633779" width="1" height="1"&gt;</description></item></channel></rss>