Read-only Filegroups on Standard Edition

  • Hi all,

    I'm exploring breaking up our reporting database (600+ GB) into several read_only filegroups for previous years records, and a read_write filegroup for the current year. We're on standard edition, so partitioning is currently out of the question, which is leading to some questions. I'm bumping into an issue with running checkfilegroup that MS documents here http://support.microsoft.com/kb/928518.

    Basically, in order to run checkfilegroup, I need to kill all existing connections, which isn't ideal. The KB suggests creating your own snapshot, but again, with standard edition, that's a no-go.

    If we upgraded to Enterprise and implemented partitioning, does that cure the issue documented in the KB, or would I have to manually create these snapshots and run checkfilegroup against them?

    From reading Paul Randal's blog http://www.sqlskills.com/BLOGS/PAUL/post/CHECKDB-From-Every-Angle-Consistency-Checking-Options-for-a-VLDB.aspx it seems like it does, but I can't find anything stating this clearly.

    Are there any other solutions other than upgrading to Enterprise in this case? Does 2008 fix this?

    Thanks for any ideas/input.

    Jeff

    - Jeff

  • You could look at using Partitioned Views. Basically, you create a table for each year then build a view over the tables. You will find more information regarding this in BOL (Books Online, the SQL Server Help System).

Viewing 2 posts - 1 through 1 (of 1 total)

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