January 14, 2010 at 6:05 am
Hello gents
Here is a question that recently draws my attention. My employer kinda need a solution to release new data into the production server from our datawarehousing server by filegroup.
A filegroup backup is made at datawarehousing server and then it should be restored into the production server to replace the same filegroup. And in the meantime, all the other old filegroups containing data under older version shall stay online and accessible.
Since I am still a newbie on filegroup restore, can this requirement be achieved without much of hassle? Or my approach is totally out of reach by SQL Server's filegroup restore feature?
regards,
Ning
Bazinga!
January 14, 2010 at 6:21 am
I don't think that can be done at all. When restoring filegroups, the primary filegroup must match the primary where the backup was taken from (ie they must be the same database). Once the filegroup is restored, log backups must be restored to bring the database to a consistent point in time.
How much data are we talking here?
Do the two systems have absolutely identical table structures?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 14, 2010 at 6:24 am
GilaMonster (1/14/2010)
I don't think that can be done at all. When restoring filegroups, the primary filegroup must match the primary where the backup was taken from (ie they must be the same database). Once the filegroup is restored, log backups must be restored to bring the database to a consistent point in time.How much data are we talking here?
Do the two systems have absolutely identical table structures?
Hello Gail
Thanks for your reply first of all. The amount of data we are talk about here is 40 filegroups with 10GB each in size. Yes, the two databases from warehousing and production are exactly the same in structure.
Bazinga!
January 14, 2010 at 6:59 am
Was one database restored initially from a backup of the other? If not, the restore will not work as SQL will consider the two to be different databases.
Bear in mind, even if they are, there's the requirement to restore log backups to get everything to the same point in time. SQL does not support moving sections of data around in filegroups. That's not what they are there for.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply