I have a database with with two filegroups - the primary and one other.
Each filegroup has its own data file. I want to restore the database to a
different database server but restore only the primary filegroup.
When I try to do this, I get the following error for each of the data files
associated with the filegroups that I did not restore - File 'data file name
'
was only partially restored by a database or file restore. The entire file
must be successfully restored before applying the log.
Any ideas?
BACKUP DATABASE test1
FILEGROUP = 'Primary'
TO primfilegroup WITH INIT
BACKUP DATABASE test1
FILEGROUP = 'FG_RW'
TO rwfilegroup WITH INIT
BACKUP LOG test1
TO test1log WITH INIT
--BACKUP LOG test1
-- TO test1log WITH NOINIT
RESTORE DATABASE test2
FILEGROUP = 'Primary'
from primfilegroup WITH NORECOVERY,
MOVE 'test1_Data' TO 'i:\test2_Data.mdf',
MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
GO
--RESTORE DATABASE test2
--FILEGROUP = 'FG_RW'
--from rwfilegroup WITH NORECOVERY,
-- MOVE 'test_RW' TO 'i:\test2_RW_Data.mdf',
-- MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
--GO
--RESTORE LOG test2
-- FROM test1log
-- WITH FILE = 1, NORECOVERY
--go
RESTORE LOG test2
FROM test1log WITH RECOVERY,
MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
GO
ERROR MESSAGE:
Msg 4320, Level 1, State 4320
File 'test_RW' was only partially restored by a database or file restore.
The entire file must be successfully restored before applying the log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.Hello, spoons
You also need to use the PARTIAL clause in the RESTORE statement. See
"partial restore operation" in Books Online.
Razvan
Showing posts with label filegroup. Show all posts
Showing posts with label filegroup. Show all posts
Wednesday, March 7, 2012
Restoring Files and Filesgroups
I have a database with with two filegroups - the primary and one other.
Each filegroup has its own data file. I want to restore the database to a
different database server but restore only the primary filegroup.
When I try to do this, I get the following error for each of the data files
associated with the filegroups that I did not restore - File 'data file name'
was only partially restored by a database or file restore. The entire file
must be successfully restored before applying the log.
Any ideas?
BACKUP DATABASE test1
FILEGROUP = 'Primary'
TO primfilegroup WITH INIT
BACKUP DATABASE test1
FILEGROUP = 'FG_RW'
TO rwfilegroup WITH INIT
BACKUP LOG test1
TO test1log WITH INIT
--BACKUP LOG test1
-- TO test1log WITH NOINIT
RESTORE DATABASE test2
FILEGROUP = 'Primary'
from primfilegroup WITH NORECOVERY,
MOVE 'test1_Data' TO 'i:\test2_Data.mdf',
MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
GO
--RESTORE DATABASE test2
--FILEGROUP = 'FG_RW'
--from rwfilegroup WITH NORECOVERY,
-- MOVE 'test_RW' TO 'i:\test2_RW_Data.mdf',
-- MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
--GO
--RESTORE LOG test2
-- FROM test1log
-- WITH FILE = 1, NORECOVERY
--go
RESTORE LOG test2
FROM test1log WITH RECOVERY,
MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
GO
ERROR MESSAGE:
Msg 4320, Level 1, State 4320
File 'test_RW' was only partially restored by a database or file restore.
The entire file must be successfully restored before applying the log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
Hello, spoons
You also need to use the PARTIAL clause in the RESTORE statement. See
"partial restore operation" in Books Online.
Razvan
Each filegroup has its own data file. I want to restore the database to a
different database server but restore only the primary filegroup.
When I try to do this, I get the following error for each of the data files
associated with the filegroups that I did not restore - File 'data file name'
was only partially restored by a database or file restore. The entire file
must be successfully restored before applying the log.
Any ideas?
BACKUP DATABASE test1
FILEGROUP = 'Primary'
TO primfilegroup WITH INIT
BACKUP DATABASE test1
FILEGROUP = 'FG_RW'
TO rwfilegroup WITH INIT
BACKUP LOG test1
TO test1log WITH INIT
--BACKUP LOG test1
-- TO test1log WITH NOINIT
RESTORE DATABASE test2
FILEGROUP = 'Primary'
from primfilegroup WITH NORECOVERY,
MOVE 'test1_Data' TO 'i:\test2_Data.mdf',
MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
GO
--RESTORE DATABASE test2
--FILEGROUP = 'FG_RW'
--from rwfilegroup WITH NORECOVERY,
-- MOVE 'test_RW' TO 'i:\test2_RW_Data.mdf',
-- MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
--GO
--RESTORE LOG test2
-- FROM test1log
-- WITH FILE = 1, NORECOVERY
--go
RESTORE LOG test2
FROM test1log WITH RECOVERY,
MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
GO
ERROR MESSAGE:
Msg 4320, Level 1, State 4320
File 'test_RW' was only partially restored by a database or file restore.
The entire file must be successfully restored before applying the log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
Hello, spoons
You also need to use the PARTIAL clause in the RESTORE statement. See
"partial restore operation" in Books Online.
Razvan
Restoring Files and Filesgroups
I have a database with with two filegroups - the primary and one other.
Each filegroup has its own data file. I want to restore the database to a
different database server but restore only the primary filegroup.
When I try to do this, I get the following error for each of the data files
associated with the filegroups that I did not restore - File 'data file name'
was only partially restored by a database or file restore. The entire file
must be successfully restored before applying the log.
Any ideas?
BACKUP DATABASE test1
FILEGROUP = 'Primary'
TO primfilegroup WITH INIT
BACKUP DATABASE test1
FILEGROUP = 'FG_RW'
TO rwfilegroup WITH INIT
BACKUP LOG test1
TO test1log WITH INIT
--BACKUP LOG test1
-- TO test1log WITH NOINIT
RESTORE DATABASE test2
FILEGROUP = 'Primary'
from primfilegroup WITH NORECOVERY,
MOVE 'test1_Data' TO 'i:\test2_Data.mdf',
MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
GO
--RESTORE DATABASE test2
--FILEGROUP = 'FG_RW'
--from rwfilegroup WITH NORECOVERY,
-- MOVE 'test_RW' TO 'i:\test2_RW_Data.mdf',
-- MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
--GO
--RESTORE LOG test2
-- FROM test1log
-- WITH FILE = 1, NORECOVERY
--go
RESTORE LOG test2
FROM test1log WITH RECOVERY,
MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
GO
ERROR MESSAGE:
Msg 4320, Level 1, State 4320
File 'test_RW' was only partially restored by a database or file restore.
The entire file must be successfully restored before applying the log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.Hello, spoons
You also need to use the PARTIAL clause in the RESTORE statement. See
"partial restore operation" in Books Online.
Razvan
Each filegroup has its own data file. I want to restore the database to a
different database server but restore only the primary filegroup.
When I try to do this, I get the following error for each of the data files
associated with the filegroups that I did not restore - File 'data file name'
was only partially restored by a database or file restore. The entire file
must be successfully restored before applying the log.
Any ideas?
BACKUP DATABASE test1
FILEGROUP = 'Primary'
TO primfilegroup WITH INIT
BACKUP DATABASE test1
FILEGROUP = 'FG_RW'
TO rwfilegroup WITH INIT
BACKUP LOG test1
TO test1log WITH INIT
--BACKUP LOG test1
-- TO test1log WITH NOINIT
RESTORE DATABASE test2
FILEGROUP = 'Primary'
from primfilegroup WITH NORECOVERY,
MOVE 'test1_Data' TO 'i:\test2_Data.mdf',
MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
GO
--RESTORE DATABASE test2
--FILEGROUP = 'FG_RW'
--from rwfilegroup WITH NORECOVERY,
-- MOVE 'test_RW' TO 'i:\test2_RW_Data.mdf',
-- MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
--GO
--RESTORE LOG test2
-- FROM test1log
-- WITH FILE = 1, NORECOVERY
--go
RESTORE LOG test2
FROM test1log WITH RECOVERY,
MOVE 'test1_Log' TO 'i:\test2_Log.ldf'
GO
ERROR MESSAGE:
Msg 4320, Level 1, State 4320
File 'test_RW' was only partially restored by a database or file restore.
The entire file must be successfully restored before applying the log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.Hello, spoons
You also need to use the PARTIAL clause in the RESTORE statement. See
"partial restore operation" in Books Online.
Razvan
Restoring filegroups in 2005.
Howdy all. I want to be able to restore just 1 filegroup from a filegroup backup, without having to restore the log afterwords even if the data has changed post filegroup backup. While this would leave the data inconsistant, it may be desired at times. From BOL: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
************************************************** ******
If the files have been modified after the file backup was created, execute the RESTORE LOG statement to apply the transaction log backup, specifying:
The name of the database to which the transaction log will be applied.
The backup device from where the transaction log backup will be restored.
The NORECOVERY clause if you have another transaction log backup to apply after the current one; otherwise, specify the RECOVERY clause.
The transaction log backups, if applied, must cover the time when the files and filegroups were backed up until the end of log (unless ALL database files are restored).
************************************************** ******
But thats just it, I may not want to take this action. Maybe some data got deleted from a set of tables in a filegroup right after I took my last filegroup backup, so I just want to restore that filegroup back to that backup, but leave my other filegroups alone. Restoring the log brings the data back to a consistant state when the log was backed up, which may not be what I want.
Can this be accomplished?
TIA, cfrA very knowledgeable guru clarified that this would not be possible.|||Only way to do this would be to restore the entire database to the desired opint in time, then transfer the data from the one filegroup to the existing database. NOTE: This will likely fail any foreign key relationships among these tables, and could result in a pile of orphaned data.
************************************************** ******
If the files have been modified after the file backup was created, execute the RESTORE LOG statement to apply the transaction log backup, specifying:
The name of the database to which the transaction log will be applied.
The backup device from where the transaction log backup will be restored.
The NORECOVERY clause if you have another transaction log backup to apply after the current one; otherwise, specify the RECOVERY clause.
The transaction log backups, if applied, must cover the time when the files and filegroups were backed up until the end of log (unless ALL database files are restored).
************************************************** ******
But thats just it, I may not want to take this action. Maybe some data got deleted from a set of tables in a filegroup right after I took my last filegroup backup, so I just want to restore that filegroup back to that backup, but leave my other filegroups alone. Restoring the log brings the data back to a consistant state when the log was backed up, which may not be what I want.
Can this be accomplished?
TIA, cfrA very knowledgeable guru clarified that this would not be possible.|||Only way to do this would be to restore the entire database to the desired opint in time, then transfer the data from the one filegroup to the existing database. NOTE: This will likely fail any foreign key relationships among these tables, and could result in a pile of orphaned data.
Restoring filegroups in 2005.
Howdy all. I want to be able to restore just 1 filegroup from a filegroup
backup, without having to restore the log afterwords even if the data has
changed post filegroup backup. While this would leave the data inconsistant,
it may be desired at times. From BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
************************************************** ******
If the files have been modified after the file backup was created, execute
the RESTORE LOG statement to apply the transaction log backup, specifying:
The name of the database to which the transaction log will be applied.
The backup device from where the transaction log backup will be restored.
The NORECOVERY clause if you have another transaction log backup to apply
after the current one; otherwise, specify the RECOVERY clause.
The transaction log backups, if applied, must cover the time when the files
and filegroups were backed up until the end of log (unless ALL database files
are restored).
************************************************** ******
But thats just it, I may not want to take this action. Maybe some data got
deleted from a set of tables in a filegroup right after I took my last
filegroup backup, so I just want to restore that filegroup back to that
backup, but leave my other filegroups alone. Restoring the log brings the
data back to a consistant state when the log was backed up, which may not be
what I want.
Can this be accomplished?
TIA, ChrisR
The short answer is that SQL Server will not assist in providing you with an inconsistent database.
A database would be inconsistent if different parts of it are from different points in time. And
this is indeed what you want to achieve.
Your option is to restore this filegroup backup to a new database (using the PARTIAL option of the
restore command - see BOL for details), and then copy over the relevant data to your production
database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
> Howdy all. I want to be able to restore just 1 filegroup from a filegroup
> backup, without having to restore the log afterwords even if the data has
> changed post filegroup backup. While this would leave the data inconsistant,
> it may be desired at times. From BOL:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
> ************************************************** ******
> If the files have been modified after the file backup was created, execute
> the RESTORE LOG statement to apply the transaction log backup, specifying:
> The name of the database to which the transaction log will be applied.
> The backup device from where the transaction log backup will be restored.
> The NORECOVERY clause if you have another transaction log backup to apply
> after the current one; otherwise, specify the RECOVERY clause.
> The transaction log backups, if applied, must cover the time when the files
> and filegroups were backed up until the end of log (unless ALL database files
> are restored).
> ************************************************** ******
> But thats just it, I may not want to take this action. Maybe some data got
> deleted from a set of tables in a filegroup right after I took my last
> filegroup backup, so I just want to restore that filegroup back to that
> backup, but leave my other filegroups alone. Restoring the log brings the
> data back to a consistant state when the log was backed up, which may not be
> what I want.
> Can this be accomplished?
> TIA, ChrisR
|||That's what I thought.
Thanks Tibor.
"Tibor Karaszi" wrote:
> The short answer is that SQL Server will not assist in providing you with an inconsistent database.
> A database would be inconsistent if different parts of it are from different points in time. And
> this is indeed what you want to achieve.
> Your option is to restore this filegroup backup to a new database (using the PARTIAL option of the
> restore command - see BOL for details), and then copy over the relevant data to your production
> database.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
>
>
backup, without having to restore the log afterwords even if the data has
changed post filegroup backup. While this would leave the data inconsistant,
it may be desired at times. From BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
************************************************** ******
If the files have been modified after the file backup was created, execute
the RESTORE LOG statement to apply the transaction log backup, specifying:
The name of the database to which the transaction log will be applied.
The backup device from where the transaction log backup will be restored.
The NORECOVERY clause if you have another transaction log backup to apply
after the current one; otherwise, specify the RECOVERY clause.
The transaction log backups, if applied, must cover the time when the files
and filegroups were backed up until the end of log (unless ALL database files
are restored).
************************************************** ******
But thats just it, I may not want to take this action. Maybe some data got
deleted from a set of tables in a filegroup right after I took my last
filegroup backup, so I just want to restore that filegroup back to that
backup, but leave my other filegroups alone. Restoring the log brings the
data back to a consistant state when the log was backed up, which may not be
what I want.
Can this be accomplished?
TIA, ChrisR
The short answer is that SQL Server will not assist in providing you with an inconsistent database.
A database would be inconsistent if different parts of it are from different points in time. And
this is indeed what you want to achieve.
Your option is to restore this filegroup backup to a new database (using the PARTIAL option of the
restore command - see BOL for details), and then copy over the relevant data to your production
database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
> Howdy all. I want to be able to restore just 1 filegroup from a filegroup
> backup, without having to restore the log afterwords even if the data has
> changed post filegroup backup. While this would leave the data inconsistant,
> it may be desired at times. From BOL:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
> ************************************************** ******
> If the files have been modified after the file backup was created, execute
> the RESTORE LOG statement to apply the transaction log backup, specifying:
> The name of the database to which the transaction log will be applied.
> The backup device from where the transaction log backup will be restored.
> The NORECOVERY clause if you have another transaction log backup to apply
> after the current one; otherwise, specify the RECOVERY clause.
> The transaction log backups, if applied, must cover the time when the files
> and filegroups were backed up until the end of log (unless ALL database files
> are restored).
> ************************************************** ******
> But thats just it, I may not want to take this action. Maybe some data got
> deleted from a set of tables in a filegroup right after I took my last
> filegroup backup, so I just want to restore that filegroup back to that
> backup, but leave my other filegroups alone. Restoring the log brings the
> data back to a consistant state when the log was backed up, which may not be
> what I want.
> Can this be accomplished?
> TIA, ChrisR
|||That's what I thought.
Thanks Tibor.
"Tibor Karaszi" wrote:
> The short answer is that SQL Server will not assist in providing you with an inconsistent database.
> A database would be inconsistent if different parts of it are from different points in time. And
> this is indeed what you want to achieve.
> Your option is to restore this filegroup backup to a new database (using the PARTIAL option of the
> restore command - see BOL for details), and then copy over the relevant data to your production
> database.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
>
>
Restoring filegroups in 2005.
Howdy all. I want to be able to restore just 1 filegroup from a filegroup
backup, without having to restore the log afterwords even if the data has
changed post filegroup backup. While this would leave the data inconsistant,
it may be desired at times. From BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
************************************************** ******
If the files have been modified after the file backup was created, execute
the RESTORE LOG statement to apply the transaction log backup, specifying:
The name of the database to which the transaction log will be applied.
The backup device from where the transaction log backup will be restored.
The NORECOVERY clause if you have another transaction log backup to apply
after the current one; otherwise, specify the RECOVERY clause.
The transaction log backups, if applied, must cover the time when the files
and filegroups were backed up until the end of log (unless ALL database files
are restored).
************************************************** ******
But thats just it, I may not want to take this action. Maybe some data got
deleted from a set of tables in a filegroup right after I took my last
filegroup backup, so I just want to restore that filegroup back to that
backup, but leave my other filegroups alone. Restoring the log brings the
data back to a consistant state when the log was backed up, which may not be
what I want.
Can this be accomplished?
TIA, ChrisRThe short answer is that SQL Server will not assist in providing you with an inconsistent database.
A database would be inconsistent if different parts of it are from different points in time. And
this is indeed what you want to achieve.
Your option is to restore this filegroup backup to a new database (using the PARTIAL option of the
restore command - see BOL for details), and then copy over the relevant data to your production
database.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
> Howdy all. I want to be able to restore just 1 filegroup from a filegroup
> backup, without having to restore the log afterwords even if the data has
> changed post filegroup backup. While this would leave the data inconsistant,
> it may be desired at times. From BOL:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
> ************************************************** ******
> If the files have been modified after the file backup was created, execute
> the RESTORE LOG statement to apply the transaction log backup, specifying:
> The name of the database to which the transaction log will be applied.
> The backup device from where the transaction log backup will be restored.
> The NORECOVERY clause if you have another transaction log backup to apply
> after the current one; otherwise, specify the RECOVERY clause.
> The transaction log backups, if applied, must cover the time when the files
> and filegroups were backed up until the end of log (unless ALL database files
> are restored).
> ************************************************** ******
> But thats just it, I may not want to take this action. Maybe some data got
> deleted from a set of tables in a filegroup right after I took my last
> filegroup backup, so I just want to restore that filegroup back to that
> backup, but leave my other filegroups alone. Restoring the log brings the
> data back to a consistant state when the log was backed up, which may not be
> what I want.
> Can this be accomplished?
> TIA, ChrisR|||That's what I thought.
Thanks Tibor.
"Tibor Karaszi" wrote:
> The short answer is that SQL Server will not assist in providing you with an inconsistent database.
> A database would be inconsistent if different parts of it are from different points in time. And
> this is indeed what you want to achieve.
> Your option is to restore this filegroup backup to a new database (using the PARTIAL option of the
> restore command - see BOL for details), and then copy over the relevant data to your production
> database.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
> > Howdy all. I want to be able to restore just 1 filegroup from a filegroup
> > backup, without having to restore the log afterwords even if the data has
> > changed post filegroup backup. While this would leave the data inconsistant,
> > it may be desired at times. From BOL:
> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
> >
> > ************************************************** ******
> > If the files have been modified after the file backup was created, execute
> > the RESTORE LOG statement to apply the transaction log backup, specifying:
> >
> > The name of the database to which the transaction log will be applied.
> > The backup device from where the transaction log backup will be restored.
> > The NORECOVERY clause if you have another transaction log backup to apply
> > after the current one; otherwise, specify the RECOVERY clause.
> > The transaction log backups, if applied, must cover the time when the files
> > and filegroups were backed up until the end of log (unless ALL database files
> > are restored).
> > ************************************************** ******
> >
> > But thats just it, I may not want to take this action. Maybe some data got
> > deleted from a set of tables in a filegroup right after I took my last
> > filegroup backup, so I just want to restore that filegroup back to that
> > backup, but leave my other filegroups alone. Restoring the log brings the
> > data back to a consistant state when the log was backed up, which may not be
> > what I want.
> >
> > Can this be accomplished?
> >
> > TIA, ChrisR
>
>
backup, without having to restore the log afterwords even if the data has
changed post filegroup backup. While this would leave the data inconsistant,
it may be desired at times. From BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
************************************************** ******
If the files have been modified after the file backup was created, execute
the RESTORE LOG statement to apply the transaction log backup, specifying:
The name of the database to which the transaction log will be applied.
The backup device from where the transaction log backup will be restored.
The NORECOVERY clause if you have another transaction log backup to apply
after the current one; otherwise, specify the RECOVERY clause.
The transaction log backups, if applied, must cover the time when the files
and filegroups were backed up until the end of log (unless ALL database files
are restored).
************************************************** ******
But thats just it, I may not want to take this action. Maybe some data got
deleted from a set of tables in a filegroup right after I took my last
filegroup backup, so I just want to restore that filegroup back to that
backup, but leave my other filegroups alone. Restoring the log brings the
data back to a consistant state when the log was backed up, which may not be
what I want.
Can this be accomplished?
TIA, ChrisRThe short answer is that SQL Server will not assist in providing you with an inconsistent database.
A database would be inconsistent if different parts of it are from different points in time. And
this is indeed what you want to achieve.
Your option is to restore this filegroup backup to a new database (using the PARTIAL option of the
restore command - see BOL for details), and then copy over the relevant data to your production
database.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
> Howdy all. I want to be able to restore just 1 filegroup from a filegroup
> backup, without having to restore the log afterwords even if the data has
> changed post filegroup backup. While this would leave the data inconsistant,
> it may be desired at times. From BOL:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
> ************************************************** ******
> If the files have been modified after the file backup was created, execute
> the RESTORE LOG statement to apply the transaction log backup, specifying:
> The name of the database to which the transaction log will be applied.
> The backup device from where the transaction log backup will be restored.
> The NORECOVERY clause if you have another transaction log backup to apply
> after the current one; otherwise, specify the RECOVERY clause.
> The transaction log backups, if applied, must cover the time when the files
> and filegroups were backed up until the end of log (unless ALL database files
> are restored).
> ************************************************** ******
> But thats just it, I may not want to take this action. Maybe some data got
> deleted from a set of tables in a filegroup right after I took my last
> filegroup backup, so I just want to restore that filegroup back to that
> backup, but leave my other filegroups alone. Restoring the log brings the
> data back to a consistant state when the log was backed up, which may not be
> what I want.
> Can this be accomplished?
> TIA, ChrisR|||That's what I thought.
Thanks Tibor.
"Tibor Karaszi" wrote:
> The short answer is that SQL Server will not assist in providing you with an inconsistent database.
> A database would be inconsistent if different parts of it are from different points in time. And
> this is indeed what you want to achieve.
> Your option is to restore this filegroup backup to a new database (using the PARTIAL option of the
> restore command - see BOL for details), and then copy over the relevant data to your production
> database.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
> > Howdy all. I want to be able to restore just 1 filegroup from a filegroup
> > backup, without having to restore the log afterwords even if the data has
> > changed post filegroup backup. While this would leave the data inconsistant,
> > it may be desired at times. From BOL:
> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073049100f0.htm
> >
> > ************************************************** ******
> > If the files have been modified after the file backup was created, execute
> > the RESTORE LOG statement to apply the transaction log backup, specifying:
> >
> > The name of the database to which the transaction log will be applied.
> > The backup device from where the transaction log backup will be restored.
> > The NORECOVERY clause if you have another transaction log backup to apply
> > after the current one; otherwise, specify the RECOVERY clause.
> > The transaction log backups, if applied, must cover the time when the files
> > and filegroups were backed up until the end of log (unless ALL database files
> > are restored).
> > ************************************************** ******
> >
> > But thats just it, I may not want to take this action. Maybe some data got
> > deleted from a set of tables in a filegroup right after I took my last
> > filegroup backup, so I just want to restore that filegroup back to that
> > backup, but leave my other filegroups alone. Restoring the log brings the
> > data back to a consistant state when the log was backed up, which may not be
> > what I want.
> >
> > Can this be accomplished?
> >
> > TIA, ChrisR
>
>
Restoring filegroups in 2005.
Howdy all. I want to be able to restore just 1 filegroup from a filegroup
backup, without having to restore the log afterwords even if the data has
changed post filegroup backup. While this would leave the data inconsistant,
it may be desired at times. From BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073
049100f0.htm
****************************************
********** ******
If the files have been modified after the file backup was created, execute
the RESTORE LOG statement to apply the transaction log backup, specifying:
The name of the database to which the transaction log will be applied.
The backup device from where the transaction log backup will be restored.
The NORECOVERY clause if you have another transaction log backup to apply
after the current one; otherwise, specify the RECOVERY clause.
The transaction log backups, if applied, must cover the time when the files
and filegroups were backed up until the end of log (unless ALL database file
s
are restored).
****************************************
********** ******
But thats just it, I may not want to take this action. Maybe some data got
deleted from a set of tables in a filegroup right after I took my last
filegroup backup, so I just want to restore that filegroup back to that
backup, but leave my other filegroups alone. Restoring the log brings the
data back to a consistant state when the log was backed up, which may not be
what I want.
Can this be accomplished?
TIA, ChrisRThe short answer is that SQL Server will not assist in providing you with an
inconsistent database.
A database would be inconsistent if different parts of it are from different
points in time. And
this is indeed what you want to achieve.
Your option is to restore this filegroup backup to a new database (using the
PARTIAL option of the
restore command - see BOL for details), and then copy over the relevant data
to your production
database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
> Howdy all. I want to be able to restore just 1 filegroup from a filegroup
> backup, without having to restore the log afterwords even if the data has
> changed post filegroup backup. While this would leave the data inconsistan
t,
> it may be desired at times. From BOL:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c0
73049100f0.htm
> ****************************************
********** ******
> If the files have been modified after the file backup was created, execute
> the RESTORE LOG statement to apply the transaction log backup, specifying:
> The name of the database to which the transaction log will be applied.
> The backup device from where the transaction log backup will be restored.
> The NORECOVERY clause if you have another transaction log backup to apply
> after the current one; otherwise, specify the RECOVERY clause.
> The transaction log backups, if applied, must cover the time when the file
s
> and filegroups were backed up until the end of log (unless ALL database fi
les
> are restored).
> ****************************************
********** ******
> But thats just it, I may not want to take this action. Maybe some data got
> deleted from a set of tables in a filegroup right after I took my last
> filegroup backup, so I just want to restore that filegroup back to that
> backup, but leave my other filegroups alone. Restoring the log brings the
> data back to a consistant state when the log was backed up, which may not
be
> what I want.
> Can this be accomplished?
> TIA, ChrisR|||That's what I thought.
Thanks Tibor.
"Tibor Karaszi" wrote:
> The short answer is that SQL Server will not assist in providing you with
an inconsistent database.
> A database would be inconsistent if different parts of it are from differe
nt points in time. And
> this is indeed what you want to achieve.
> Your option is to restore this filegroup backup to a new database (using t
he PARTIAL option of the
> restore command - see BOL for details), and then copy over the relevant da
ta to your production
> database.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
>
>
backup, without having to restore the log afterwords even if the data has
changed post filegroup backup. While this would leave the data inconsistant,
it may be desired at times. From BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c073
049100f0.htm
****************************************
********** ******
If the files have been modified after the file backup was created, execute
the RESTORE LOG statement to apply the transaction log backup, specifying:
The name of the database to which the transaction log will be applied.
The backup device from where the transaction log backup will be restored.
The NORECOVERY clause if you have another transaction log backup to apply
after the current one; otherwise, specify the RECOVERY clause.
The transaction log backups, if applied, must cover the time when the files
and filegroups were backed up until the end of log (unless ALL database file
s
are restored).
****************************************
********** ******
But thats just it, I may not want to take this action. Maybe some data got
deleted from a set of tables in a filegroup right after I took my last
filegroup backup, so I just want to restore that filegroup back to that
backup, but leave my other filegroups alone. Restoring the log brings the
data back to a consistant state when the log was backed up, which may not be
what I want.
Can this be accomplished?
TIA, ChrisRThe short answer is that SQL Server will not assist in providing you with an
inconsistent database.
A database would be inconsistent if different parts of it are from different
points in time. And
this is indeed what you want to achieve.
Your option is to restore this filegroup backup to a new database (using the
PARTIAL option of the
restore command - see BOL for details), and then copy over the relevant data
to your production
database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
> Howdy all. I want to be able to restore just 1 filegroup from a filegroup
> backup, without having to restore the log afterwords even if the data has
> changed post filegroup backup. While this would leave the data inconsistan
t,
> it may be desired at times. From BOL:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2f552700-efb3-48f1-b96d-c0
73049100f0.htm
> ****************************************
********** ******
> If the files have been modified after the file backup was created, execute
> the RESTORE LOG statement to apply the transaction log backup, specifying:
> The name of the database to which the transaction log will be applied.
> The backup device from where the transaction log backup will be restored.
> The NORECOVERY clause if you have another transaction log backup to apply
> after the current one; otherwise, specify the RECOVERY clause.
> The transaction log backups, if applied, must cover the time when the file
s
> and filegroups were backed up until the end of log (unless ALL database fi
les
> are restored).
> ****************************************
********** ******
> But thats just it, I may not want to take this action. Maybe some data got
> deleted from a set of tables in a filegroup right after I took my last
> filegroup backup, so I just want to restore that filegroup back to that
> backup, but leave my other filegroups alone. Restoring the log brings the
> data back to a consistant state when the log was backed up, which may not
be
> what I want.
> Can this be accomplished?
> TIA, ChrisR|||That's what I thought.
Thanks Tibor.
"Tibor Karaszi" wrote:
> The short answer is that SQL Server will not assist in providing you with
an inconsistent database.
> A database would be inconsistent if different parts of it are from differe
nt points in time. And
> this is indeed what you want to achieve.
> Your option is to restore this filegroup backup to a new database (using t
he PARTIAL option of the
> restore command - see BOL for details), and then copy over the relevant da
ta to your production
> database.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:5774CAB8-3FAC-4DF6-BCF8-1FA12E73559E@.microsoft.com...
>
>
Restoring filegroup which has indexes only
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 an
d
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 ?
>
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 an
d
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 ?
>
Restoring filegroup which has indexes only
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 ?
>
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 ?
>
Restoring filegroup which has indexes only
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 ?
>
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 ?
>
restoring filegroup from different date than mdf file
Can anyone tell me what the effect would be of restoring a filegroup from an
older date than the other filegroups in the database.
The tables in the older filegroup contain fewer records than the current
one. My main concern is that the sysindexes table will still contain
reference to a greater number of records.
You would not be able to access the database until you have restore all subsequent transaction log
backups for the database until current point in time. This is better explained in Books Online...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:475C96EA-967D-4200-95ED-F1038F4488E0@.microsoft.com...
> Can anyone tell me what the effect would be of restoring a filegroup from an
> older date than the other filegroups in the database.
> The tables in the older filegroup contain fewer records than the current
> one. My main concern is that the sysindexes table will still contain
> reference to a greater number of records.
older date than the other filegroups in the database.
The tables in the older filegroup contain fewer records than the current
one. My main concern is that the sysindexes table will still contain
reference to a greater number of records.
You would not be able to access the database until you have restore all subsequent transaction log
backups for the database until current point in time. This is better explained in Books Online...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:475C96EA-967D-4200-95ED-F1038F4488E0@.microsoft.com...
> Can anyone tell me what the effect would be of restoring a filegroup from an
> older date than the other filegroups in the database.
> The tables in the older filegroup contain fewer records than the current
> one. My main concern is that the sysindexes table will still contain
> reference to a greater number of records.
restoring filegroup from different date than mdf file
Can anyone tell me what the effect would be of restoring a filegroup from an
older date than the other filegroups in the database.
The tables in the older filegroup contain fewer records than the current
one. My main concern is that the sysindexes table will still contain
reference to a greater number of records.You would not be able to access the database until you have restore all subsequent transaction log
backups for the database until current point in time. This is better explained in Books Online...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:475C96EA-967D-4200-95ED-F1038F4488E0@.microsoft.com...
> Can anyone tell me what the effect would be of restoring a filegroup from an
> older date than the other filegroups in the database.
> The tables in the older filegroup contain fewer records than the current
> one. My main concern is that the sysindexes table will still contain
> reference to a greater number of records.
older date than the other filegroups in the database.
The tables in the older filegroup contain fewer records than the current
one. My main concern is that the sysindexes table will still contain
reference to a greater number of records.You would not be able to access the database until you have restore all subsequent transaction log
backups for the database until current point in time. This is better explained in Books Online...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:475C96EA-967D-4200-95ED-F1038F4488E0@.microsoft.com...
> Can anyone tell me what the effect would be of restoring a filegroup from an
> older date than the other filegroups in the database.
> The tables in the older filegroup contain fewer records than the current
> one. My main concern is that the sysindexes table will still contain
> reference to a greater number of records.
Restoring File Backups II
Sorry, I want restore only two files ( one filegroup) of
database ( not full backup). I don't have the transaction
log backups created since the file backups. I don't care
about changes. I want restore only files and (optional)
last log backup.Typically file backups can only be restored on the same database where they
were performed. If you want to restore them to a different database, then
starting point for such a restore has to be a complete backup. If you want
to restore these file/filegroup backups to a different database then follow
the steps below :
- Restore complete backup with standby
- Restore all file/filegroup backups with standby
- Use DTS or BCP to get the data out of the filegroups (since you cannot
bring the restore database online unless you apply all transaction log
backups)
Also, you cannot restore only the last log backup. If you need changes from
the last log, you WILL need all log backups from the latest filegroup
backup that you applied.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
database ( not full backup). I don't have the transaction
log backups created since the file backups. I don't care
about changes. I want restore only files and (optional)
last log backup.Typically file backups can only be restored on the same database where they
were performed. If you want to restore them to a different database, then
starting point for such a restore has to be a complete backup. If you want
to restore these file/filegroup backups to a different database then follow
the steps below :
- Restore complete backup with standby
- Restore all file/filegroup backups with standby
- Use DTS or BCP to get the data out of the filegroups (since you cannot
bring the restore database online unless you apply all transaction log
backups)
Also, you cannot restore only the last log backup. If you need changes from
the last log, you WILL need all log backups from the latest filegroup
backup that you applied.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Restoring File Backups II
Sorry, I want restore only two files ( one filegroup) of
database ( not full backup). I don't have the transaction
log backups created since the file backups. I don't care
about changes. I want restore only files and (optional)
last log backup.
Typically file backups can only be restored on the same database where they
were performed. If you want to restore them to a different database, then
starting point for such a restore has to be a complete backup. If you want
to restore these file/filegroup backups to a different database then follow
the steps below :
- Restore complete backup with standby
- Restore all file/filegroup backups with standby
- Use DTS or BCP to get the data out of the filegroups (since you cannot
bring the restore database online unless you apply all transaction log
backups)
Also, you cannot restore only the last log backup. If you need changes from
the last log, you WILL need all log backups from the latest filegroup
backup that you applied.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
database ( not full backup). I don't have the transaction
log backups created since the file backups. I don't care
about changes. I want restore only files and (optional)
last log backup.
Typically file backups can only be restored on the same database where they
were performed. If you want to restore them to a different database, then
starting point for such a restore has to be a complete backup. If you want
to restore these file/filegroup backups to a different database then follow
the steps below :
- Restore complete backup with standby
- Restore all file/filegroup backups with standby
- Use DTS or BCP to get the data out of the filegroups (since you cannot
bring the restore database online unless you apply all transaction log
backups)
Also, you cannot restore only the last log backup. If you need changes from
the last log, you WILL need all log backups from the latest filegroup
backup that you applied.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Restoring File Backups II
Sorry, I want restore only two files ( one filegroup) of
database ( not full backup). I don't have the transaction
log backups created since the file backups. I don't care
about changes. I want restore only files and (optional)
last log backup.Typically file backups can only be restored on the same database where they
were performed. If you want to restore them to a different database, then
starting point for such a restore has to be a complete backup. If you want
to restore these file/filegroup backups to a different database then follow
the steps below :
- Restore complete backup with standby
- Restore all file/filegroup backups with standby
- Use DTS or BCP to get the data out of the filegroups (since you cannot
bring the restore database online unless you apply all transaction log
backups)
Also, you cannot restore only the last log backup. If you need changes from
the last log, you WILL need all log backups from the latest filegroup
backup that you applied.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
database ( not full backup). I don't have the transaction
log backups created since the file backups. I don't care
about changes. I want restore only files and (optional)
last log backup.Typically file backups can only be restored on the same database where they
were performed. If you want to restore them to a different database, then
starting point for such a restore has to be a complete backup. If you want
to restore these file/filegroup backups to a different database then follow
the steps below :
- Restore complete backup with standby
- Restore all file/filegroup backups with standby
- Use DTS or BCP to get the data out of the filegroups (since you cannot
bring the restore database online unless you apply all transaction log
backups)
Also, you cannot restore only the last log backup. If you need changes from
the last log, you WILL need all log backups from the latest filegroup
backup that you applied.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)