Redistributing Data Across Files

Question

Redistributing Data Across Files

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply

chuck.hamilton SSCommitted Points: 1537 More actions · Answer 1

I'v not done much in the cloud because of all the crippling restrictions it imposes on SQL Server. Especially Azure SQL. Are you saying that the backend storage in Azure (or possibly AWS) is not striped across many spindles as it is with an on-prem SAN?

Steve Jones - SSC Editor SSC Guru Points: 734449 More actions · Answer 2

It is not. They have high end storage available, but limited paths for each set of disks. Therefore, this will apply.

jk.capoeira Valued Member Points: 60 More actions · Answer 3

a bit out of topic, but sometimes you want to investigate /correct an issue on a big table in production. But you don't want to do a backup restore to another environment because of disks pace and settings you need to correct first. So I read somewhere that it is possible to move that table to anther file group, create a backup of that file group and restore that on the uat environment. It would be nice to have some blog about that to learn more.

BobMcC SSCrazy Points: 2260 More actions · Answer 4

Steve,

Why not just create a new permanent filegroup with the required number of files in it; and move the data once? It seems like a lot of work to move the data twice to balance it. The only advantage I see would be to keep it under the default primary file group.

Thanks,

Bob McCormick

Steve Jones - SSC Editor SSC Guru Points: 734449 More actions · Answer 5

Creating a new filegroup for everything does not always work. Space constraints are one reason for this.

This isn't to imply the solution is the only one or the one that should always be used, but to show a way to balance out your files if needed.