websss
asked on
advice and help moving to partitioning
I've got a busy 24/7 database that is quickly running out of space, we have another 3.5 TB nvme drive that i would like to use
We have sql 2017 ent, so I know partitioning is supported
My initial questions are
1) can i partition while the database is in use
2) can I move "new data" or the "old data" to the other drive and just use these 2 drives (until we move to new server and setup differently)
3) are there any considerations with performance, SP's, backups etc that are different with partitions#
4) what are the rough steps involved to do this? i would ideally like new data to start saving to the new drive, and keep the existing data on the current 3.5tb nvme drive
I'm a newbie to partitions so would appreciate any gotcha advice and a rough plan of action to do while keeping online
We have sql 2017 ent, so I know partitioning is supported
My initial questions are
1) can i partition while the database is in use
2) can I move "new data" or the "old data" to the other drive and just use these 2 drives (until we move to new server and setup differently)
3) are there any considerations with performance, SP's, backups etc that are different with partitions#
4) what are the rough steps involved to do this? i would ideally like new data to start saving to the new drive, and keep the existing data on the current 3.5tb nvme drive
I'm a newbie to partitions so would appreciate any gotcha advice and a rough plan of action to do while keeping online
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.