March 27, 2008 at 1:31 pm
I am doing my first sql2005 ent. ed sp1 database snapshot tonight of a prod dbase that is 180 gig. In test more frequently
We are doing an update in small chunks to a large table so I thought it would be a good time to try it.
I am pretty sure I will be fine and plan to get rid of it in the morning
Questions:
1:How bad is that performance hit due to the copy write operation to the snapshot?
2:even though it carves out all the db files I see it really does not take up the disk space?
3: dropping it is simple enough
4: Is this a good use for a script that will update 24 million rows in small chunks.
5: anything I missed.
Just trying to get a warm and fuzzy feeling.
March 28, 2008 at 9:48 am
1. As long as you perform DML operations in small chunks it should'nt be a problem.
2. Since the snapshot uses sparse files it the more modifications you perform to source database the more the snapshot grows in size
3. Yep I agree
4. Difficult to answer. I think you might end up running out of disk space if there no available disk space
5. Nothing else I believe.
[font="Verdana"]- Deepak[/font]
March 28, 2008 at 1:35 pm
You didn't describe your disk configuration, which greatly affects your question about system response.
March 29, 2008 at 3:02 pm
If drive space is constraint, you can create new database snapshot after every update in chnuk. This way disk space issue will be minimal .
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply