June 17, 2014 at 8:10 am
I am redesigning the filegroups for a database that is used for data processing. Data will be loaded into various tables that will be created on filegroups that are on different drives. Large range queries will be then run against the tables in parallel. The reasoning for this is to isolate IO.
My question is whether there is any value in having a filegroup besides a PRIMARY for other tables. We are not looking to use piecemeal restores or anthing like that for this database, so I am not sure the concept of having a tiny filegroup just for system objects has any validity here.
Any advice or input is appreciated. Thanks in advance.
June 17, 2014 at 12:17 pm
Hard to say based on the information at hand. For most databases less than 200gb, I had everything in primary and it all worked well enough.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply