Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Operating system Error 112


Operating system Error 112

Author
Message
magarity kerns
magarity kerns
Old Hand
Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)

Group: General Forum Members
Points: 384 Visits: 397
Look. the straight copy all from the script doesn't have any kind of sorting or anything to make a lot of overhead - do you really have production servers that are so heavily loaded they can't handle a one time copy like I've suggested at some time during the week? Sounds like an upgrade is in order! Besides, compared to the original article's suggestion, I'm sure my ideas are much better all around. Since the problem is to go to a computer that has a FAT32 drive without enough space to handle the full log, I can't think of any other ways to do it.
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47212 Visits: 44368
magarity kerns (4/18/2009)
Look. the straight copy all from the script doesn't have any kind of sorting or anything to make a lot of overhead - do you really have production servers that are so heavily loaded they can't handle a one time copy like I've suggested at some time during the week?


I've worked on databases that are mission critical, heavily used and over 1 TB in size, where a script of all the data will take some hours, during which the increased IO and the flushing of data from cache will degrade performance beyond what's acceptable.

If you DBs aren't that heavily used and are small enough that the copy won't take hours, great. I'm just pointing out that it's not the case for every system and that all methods to copy databases have some advantages and some disadvantages.


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


magarity kerns
magarity kerns
Old Hand
Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)

Group: General Forum Members
Points: 384 Visits: 397
I never deal with anything mission critical so I'll take your word for it; my own experience is 100% data warehouses where even if there is a lot of data, they're loaded in the wee hours of the night, the reporting services grind out reports before everyone comes to work and then during the day it's all data miners and other ad-hocs who expect moderate to long query times anyway. So doing the direct connection copy all objects method is just yet another long running daytime query. That's how I used to repopulate the development database from time to time and no one ever noticed it to complain. I haven't actually done the script out including data to a .sql file on a 'real' database; I admit that would be a horrendous size text file. I was throwing it out as something to consider as a better possibility than the original.
Hotfix
Hotfix
SSC Rookie
SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)

Group: General Forum Members
Points: 35 Visits: 651
This article was in pending for several months and posted now on how I have performed/achieved in backup and restore of a 200 GB production db to a FAT32.

Thoughts and ideas are always welcome.

Mahidhar Vattem
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search