Automating DB Snapshots

Question

Automating DB Snapshots

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

They are usually smaller than the source database. They contain the original version of pages that change in the source database.

Still, ask yourself how much of that source database changes in a week? In a month? In a year?

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

krypto69 SSChampion Points: 13604 More actions · Answer 2

Okay thanks for the advise everyone...

I'm going to create a test DB and start creating snapshots. Guess that's the only way I can really tell how big my snapshots will be(?)

After reading all of your comments, I think at the very least, I would create another DB server that is a copy of the existing and create my snapshots off of that, as to not mess with production.

Thanks again everyone! Happy Holidays

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 3

Doing that, you are probably going to need to looking to mirroring your databases. As this would be for reporting, I'd look at asyncronous mirroring of the reporting database.

I don't think you could use log shipping to keep the second database in sync with the primary database. The other choice may be replication.