Re: SQL Server 2005 - filegroup backup/restore problem

Erland,
thank you for warm words.

Since I don't use extra filegroups much, I had to consult with MVP colleagues, who confirmed my suspicion that you can't do what
you seem to be wanting to.

To be able to access the table, you can backup the log again, and
the restore that log. That will bring the filegroup in sync with the
rest of the database. However, you will find that the table is
empty.

Yes indeed, this is the solution. Thank's for the idea! I tried it and it works. Of course, I still have a problem of empty table after last backup/restore+recovery. I will try STOPAT tomorrow, maybe it will help.
Anyway, now I can recover the database and make it online. That is a step forward.
Darek


The reason your scheme does not work, is that SQL Server does not know
what else might have happened in the database. Say that there is a SalesOrder table which is in the Primary group. Say also that after the distaster DELETE, you also deleted order 11000 in the parent table.
If the filegroup would be available after the filegroup restore, there
would now be rows in SalesOrderDetail that violated an FK constraint.
That is impermissible.


.