re: Filegroups and Non-Clustered Indexes
Well, if you have some "write this" commands, it can be better to involve multiple disk controllers, rather than having it all go through the one.
View Articlere: Filegroups and Non-Clustered Indexes
Hi, Rob, good post. Can you explain more about "it can be nice to have transactions which update both the clustered and non-clustered indexes using different disks", better with a quick example? Just a...
View Articlere: Filegroups and Non-Clustered Indexes
Yeah, there are a bunch of reasons to think carefully about index storage. I really think they deserve to be considered more carefully that they typically are.
View Articlere: Filegroups and Non-Clustered Indexes
Also, even append-only workloads might fragment a table and its index to 100% if both are on the same filegroup (even if nothing else is on that filegroup). They might get every other extent allocated....
View Articlere: Filegroups and Non-Clustered Indexes
Hi Rob...As I understand it, the DEFAULT filegroup only comes into play when you do a CREATE TABLE. In other words, if no ON clause is specified with the CREATE TABLE command, it's created on the...
View Articlere: Filegroups and Non-Clustered Indexes
Hi Andrew,When the volumes are all part of the same drive, I do find myself wondering if it's worth separating them out or not. Generally, multiple volumes that map to the same physical drive array are...
View Articlere: Filegroups and Non-Clustered Indexes
Hey Rob, do you normally still go to the trouble of putting indexes in a separate filegroup on a separate disk when the disks presented to the server are all part of the same RAID array? Cheers.
View Articlere: Filegroups and Non-Clustered Indexes
Hi Vijay,I wouldn't worry. Separating indexes off is far less important than the things you've suggested around having separate disks for data files, log files, and tempdb. You could put your backups...
View Articlere: Filegroups and Non-Clustered Indexes
Rob,We already have everything on a single filegroup for a small business standard edition of SQL Server 2008 R2 database. Database size is 30 GB approximately.We are going to move the already existing...
View Article
