Posted by John Bell on 11/12/05 22:20

Hi

From "How to restore files and filegroups over existing files (Enterprise
Manager)" in BOL

Under Recovery completion state, do one of the following:
a.. Click Leave database operational. No additional transaction logs can
be restored if no further transaction log backups are to be applied.


b.. Click Leave database nonoperational, but able to restore additional
transaction logs if another transaction log backup is to be applied
It seems that the log file backup was not taken before the filegroup backup.
If you were not going to restore the logs then the 'Leave database
operational' should be checked.

HTH

John

<si.downes@gmail.com> wrote in message
news:1131487927.857991.20510@o13g2000cwo.googlegroups.com...
> Using SQL Server 2000 SP3 I'm developing a data warehouse where data
> will be archived off to a filegroup, this filegroup backed up and the
> tables in this filegroup truncated to free up space on the server.
>
> So using Enterprise Manager I've copied data to the filegroup tables,
> backed up the file group, truncated the tables, but when I have
> restored the file group the database is stuck in a state of
> '(loading...)' and I can't get it to resume. I've tried running the
> command RESTORE LOG databaseName WITH RECOVERY but get an error message
> that the database has been restored to different time (sorry I can't
> remember exact syntax but I'm not at my work computer)
>
> Is this familiar to anyone? Ignoring the filegroups is there a way I
> can get the database .MDF back up and running?
>
> Thanks
>

[Back to original message]