Prev: Filegroup restore used to selectively refresh filegroup in 2nd db.
Next: Problem with Implicit conversion of varchar value to varchar cannot be performed because the collation of the value is unresolved due to a collation conflict
From: CqlBoy on 14 May 2010 14:16
I have TestDB1 comprised of 5 filegroups, which I've completed full/log
backups to to restore as TestDB2. When data changes within one filegroup on
TestDB1, I've taken a diff' + tlog backup and tried to use it to restore on
TestDB2 so that same filegroup would be essentially refreshed. My execution
sequence uses the last full, last diff', and tlog from TestDB1 but this
doesn't work? Why? Is there a way to do this ? Thx. - CqlBoy

Message applying full backup:
>Processed 16 pages for database 'FGTestRestore', file 'FGTest_fg2' on file 1.
>RESTORE DATABASE ... FILE=<name> successfully processed 16 pages in 0.026 >seconds (4.807 MB/sec).

Message applying diff' backup:
>Processed 16 pages for database 'FGTestRestore', file 'FGTest_fg2' on file 1.
>RESTORE DATABASE ... FILE=<name> successfully processed 16 pages in 0.020 >seconds (6.250 MB/sec).

Message applying diff' log backup:
>Msg 3116, Level 16, State 1, Line 2
>The supplied backup is not on the same recovery path as the database, and is >ineligible for use for an online file restore.
>Msg 3013, Level 16, State 1, Line 2
>RESTORE DATABASE is terminating abnormally.
From: Erland Sommarskog on 14 May 2010 15:34
CqlBoy (CqlBoy(a)discussions.microsoft.com) writes:
> I have TestDB1 comprised of 5 filegroups, which I've completed full/log
> backups to to restore as TestDB2. When data changes within one
> filegroup on TestDB1, I've taken a diff' + tlog backup and tried to use
> it to restore on TestDB2 so that same filegroup would be essentially
> refreshed. My execution sequence uses the last full, last diff', and
> tlog from TestDB1 but this doesn't work? Why? Is there a way to do
> this ? Thx. - CqlBoy

You posted a similar question yesterday, to which I posted an answer. For
your convenience, I repeat my answer here:

You can't make it work. You may know that the changes made to the
second filegroup does not cause any violations, but SQL Server doesn't.
Say that FG2 includes a table Products, and FG1 has the table
OrdersDetails. Now in the source database, you delete a product, all
order details where it is referred to. If you were able to restore FG2
in the target databasee, that database would now have OrderDetails with
non-existing products. Still there would be a foreign-key constraint
that would be marked as trusted. That can count as nothing but
corruption.





--
Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

 | 
Pages: 1
Prev: Filegroup restore used to selectively refresh filegroup in 2nd db.
Next: Problem with Implicit conversion of varchar value to varchar cannot be performed because the collation of the value is unresolved due to a collation conflict