a) Adding two new filegroups b) Adding files on those drives to those new filegroups c) Moving two of the tables...
to those new filegroups
...But the real issue for splitting data across different drives is how much I/O there is to the tables in question. Even if they are large, that's not so much of an issue if they aren't used heavily. Look at which data is causing the main I/O.
Dig Deeper on SQL Server Database Modeling and Design
Related Q&A from Greg Low
Should developers be granted permissions to production queue in a SQL Server environment? See why expert Greg Low suggests proc access by WITH ... Continue Reading
If you're working with SQL Server 2000 and trying to find a disabled index, here's something you should know. Continue Reading
Find how to save stored procedure output to the network drive via SQL Server Management Studio. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.