Filegroup restore problems

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?

ThanksHi

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.googlegro ups.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|||Hi,

try the command
restore database 'yourdatabase' 'with NORECOVERY

it will then disable loading state ... read restore in BOL with very
carefully theirs a option of norecovery in it , BOL is your friend.

ActiveCrypt
---------
http://www.activecrypt.com

File Restore Problems

We have backed up a SQL 7.0 database to disk and am now
trying to restore it using the with move option to a
different device and with a different name.
The restore starts and fails after a fairly small amount
of time with the following message:
fcb::ZeroFile(): GetOverLappedResult() failed with error 2
It appears to initially create the .mdf file but deletes
it after the above message is received.
We have searched the web and found very little about this
problem. I suspect physical disk problems. I can restire
other smaller databases to the same device using the same
method with no trouble - but anything bigger fails also.
Anybody had anything similar and what did you do to
resolve the problem.
Thanks
David
I think the first step is to check your hardware (HD and RAID controller if
present) and then go to another issues linked with MS SQL errors... but for
me it's 99% a hardware problems
"David" <dave.whitehead@.cis.co.uk> wrote in message
news:dec601c43c15$89472f20$a401280a@.phx.gbl...
> We have backed up a SQL 7.0 database to disk and am now
> trying to restore it using the with move option to a
> different device and with a different name.
> The restore starts and fails after a fairly small amount
> of time with the following message:
> fcb::ZeroFile(): GetOverLappedResult() failed with error 2
> It appears to initially create the .mdf file but deletes
> it after the above message is received.
> We have searched the web and found very little about this
> problem. I suspect physical disk problems. I can restire
> other smaller databases to the same device using the same
> method with no trouble - but anything bigger fails also.
> Anybody had anything similar and what did you do to
> resolve the problem.
|||Try coping a large file to the destination drive(size almost similar to the database), using windows explorer and check what error do you get. Also check if any disk quota has been set.

File Restore Problems

We have backed up a SQL 7.0 database to disk and am now
trying to restore it using the with move option to a
different device and with a different name.
The restore starts and fails after a fairly small amount
of time with the following message:
fcb::ZeroFile(): GetOverLappedResult() failed with error 2
It appears to initially create the .mdf file but deletes
it after the above message is received.
We have searched the web and found very little about this
problem. I suspect physical disk problems. I can restire
other smaller databases to the same device using the same
method with no trouble - but anything bigger fails also.
Anybody had anything similar and what did you do to
resolve the problem.
Thanks
DavidI think the first step is to check your hardware (HD and RAID controller if
present) and then go to another issues linked with MS SQL errors... but for
me it's 99% a hardware problems
"David" <dave.whitehead@.cis.co.uk> wrote in message
news:dec601c43c15$89472f20$a401280a@.phx.gbl...
> We have backed up a SQL 7.0 database to disk and am now
> trying to restore it using the with move option to a
> different device and with a different name.
> The restore starts and fails after a fairly small amount
> of time with the following message:
> fcb::ZeroFile(): GetOverLappedResult() failed with error 2
> It appears to initially create the .mdf file but deletes
> it after the above message is received.
> We have searched the web and found very little about this
> problem. I suspect physical disk problems. I can restire
> other smaller databases to the same device using the same
> method with no trouble - but anything bigger fails also.
> Anybody had anything similar and what did you do to
> resolve the problem.|||Try coping a large file to the destination drive(size almost similar to the
database), using windows explorer and check what error do you get. Also chec
k if any disk quota has been set.

File Restore Problems

We have backed up a SQL 7.0 database to disk and am now
trying to restore it using the with move option to a
different device and with a different name.
The restore starts and fails after a fairly small amount
of time with the following message:
fcb::ZeroFile(): GetOverLappedResult() failed with error 2
It appears to initially create the .mdf file but deletes
it after the above message is received.
We have searched the web and found very little about this
problem. I suspect physical disk problems. I can restire
other smaller databases to the same device using the same
method with no trouble - but anything bigger fails also.
Anybody had anything similar and what did you do to
resolve the problem.
Thanks
DavidI think the first step is to check your hardware (HD and RAID controller if
present) and then go to another issues linked with MS SQL errors... but for
me it's 99% a hardware problems
"David" <dave.whitehead@.cis.co.uk> wrote in message
news:dec601c43c15$89472f20$a401280a@.phx.gbl...
> We have backed up a SQL 7.0 database to disk and am now
> trying to restore it using the with move option to a
> different device and with a different name.
> The restore starts and fails after a fairly small amount
> of time with the following message:
> fcb::ZeroFile(): GetOverLappedResult() failed with error 2
> It appears to initially create the .mdf file but deletes
> it after the above message is received.
> We have searched the web and found very little about this
> problem. I suspect physical disk problems. I can restire
> other smaller databases to the same device using the same
> method with no trouble - but anything bigger fails also.
> Anybody had anything similar and what did you do to
> resolve the problem.|||Try coping a large file to the destination drive(size almost similar to the database), using windows explorer and check what error do you get. Also check if any disk quota has been set