October 24, 2016 at 1:57 pm
Many of our databases have monthly archived tables that reside in filegroups for that specified year. For example, we have Table_2016_01, Table_2016_02, etc and all of those would be in Filegroup_2016. Our problem is that we have some dating back to the early 2000s that we don't actively use but need to hold on to. Is there a way to take a specified filegroup(s) "offline" so that they are not part of the active filegroups, therefore, improving IO and maintenance tasks? I don't really want to move the old tables to their own database or rely on taking a backup and then having to restore from it in the event that a table is needed. I'm thinking more along the lines of somehow moving the filegroups to an offline storage area where I'll be able to move them back and attach them to the database if need be. Does something like that exist?
October 24, 2016 at 2:41 pm
If you set such file groups to "Read Only", they not only won't need index maintenance but they also won't need to be backed up on every full backup.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2016 at 5:00 pm
They are set to read-only now but it's not specified to not include them in the backups. I was also hoping to move them out of sight without having to worry about messing with permissions.
October 31, 2016 at 7:40 am
I wanted to give this a bump in case someone missed it last week and can provide information on what I'm trying to do.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply