If you have LOBs, you won't be able to rebuild indexes online. Also keep in mind that online index rebuilds will lock the table at the beginning and end...

You can do a search on that topic as there are a lot of articles/blogs people have written. It essentially allows SQL Server to 'lock pages in memory' instead...

Another thing I just thought about is if your cache hit ratio is low. Perhaps the performance dashboard/Perfmon can assist in diagnosing the server. Sorry, I'm just thinking...

Just to get the ball rolling, I would run Perfmon to find out where the bottlenecks are. It doesn't look like it's memory, but perhaps it could be IO?...

Then perhaps you can take a look at the execution plan and go from there...

Ahh, that's what it was... OFFLINE/ONLINE after the modify file... Thanks!

Perhaps SQL Server is consuming all of the server's memory. Can you verify that SQL Server has a max/min memory limit? Also, there are some things you may...

Thanks for correcting my previous "answer"! 😀

I have never encountered that error, but these questions may help...

Have you looked in the SQL Security tab and verify your account has the necessary permissions?

Perhaps verify that...

Please verify this, but I believe you can do a modify file to the new location, then do a restart on SQL service via the Configuration Manager.

Perhaps SQL Service Account doesn't have permissions to the folder? What is the error message when you try to do a restore?

Do you have an index that will satisfy the query? Do you need to select all of the columns?

Nevermind... I found out the answer which is to use the partitioning function. I was like 'Duh'... It's been that kinda week for me... 😛

An idea came to my head... Surprising, I know...

I will be using Gail's idea of moving data into a temp table incrementally into the new FileGroup. Is there...

Hehe, I never really thought of that as an option! I feel silly now... 😛

Thank you once again, Gail!