We are planning to put our tables on one filegroup and the indexes on the
other. In SQL 2005, it is possible to restore just 1 filegroup and continue
operations. This sounds fine if the tables and the associated indexes are on
the same filegroup. But what happens in my case ? If the index filegroup
drive fails and is restored from a backup, the indexes on it will be out of
sync. My question is - will we have to rebuild all the indexes (in which
case, it won't make sense to restore the filegroup in the first place), and
is it actually possible to restore the filegroup which holds indexes only and
continue operations as normal, or would it cause problems ?Hi Pranil
If you restore a filegroup, you must also restore log backups to bring the
filegroup up to date (i.e. get it in sync) with the rest of the database.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Pranil" <Pranil@.discussions.microsoft.com> wrote in message
news:05780582-E1EA-4EF6-94CF-D19982EAB574@.microsoft.com...
> We are planning to put our tables on one filegroup and the indexes on the
> other. In SQL 2005, it is possible to restore just 1 filegroup and
> continue
> operations. This sounds fine if the tables and the associated indexes are
> on
> the same filegroup. But what happens in my case ? If the index filegroup
> drive fails and is restored from a backup, the indexes on it will be out
> of
> sync. My question is - will we have to rebuild all the indexes (in which
> case, it won't make sense to restore the filegroup in the first place),
> and
> is it actually possible to restore the filegroup which holds indexes only
> and
> continue operations as normal, or would it cause problems ?
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment