| Author |
Topic |
|
dbthj
Posting Yak Master
143 Posts |
 Posted - 2008-08-17 : 16:30:13
|
| SQL 2000Windows 2003 SP1Error:Insufficient system resources exist to complete the requested service. 0 file(s) copied.What I am trying to do: Move database data file to a different drive.Copy Method: After DETACHing the database, I wanted to copy a 69 GIG .mdf file from D: drive to E: drive.I tried 2 methods. First a gui copy/paste. Then I tried a dos copy command from a command prompt.The error message is the same.SPACE DOES NOT APPEAR TO BE AN ISSUE.The destination drive has 150 GB free. The file I am trying to copyis 69 GB. I was able to copy files nearly that big that were .txt files.Didn't have space to create test files 69 GB on the source drive.This process worked fine for some smaller .mdf files of other databases. It was simple. detach, copy files, attach. No sweat.Does SQL Server keep some hooks in the file even after it is detached? I am mystified. My Windows Admin guys don't know. |
|
|
Transact Charlie
Master Smack Fu Yak Hacker
3451 Posts |
Posted - 2008-08-17 : 16:59:02
|
| HI dbthj,I think you've run into a buffered file copy error which, apparently is quite commen when copying big database files.Check out technet for some good info,start at : http://blogs.technet.com/askperf/archive/2007/05/08/slow-large-file-copy-issues.aspxThere's a tool called ESEUTIL which exists on exchange servers which will help you out (it's good for copying really big files) - you should also be able to get a copy from technet somewhere.Good luck-------------Charlie |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-08-17 : 21:45:59
|
| It's not sql issue rather os ones, how much memory does the server have? |
|
|
|
Transact Charlie
Master Smack Fu Yak Hacker
3451 Posts |
Posted - 2008-08-18 : 05:23:49
|
| Why are you still on 2003 service pack 1?Can you not upgrade to sp2? Might fix your problem if this is a buffered copy operation.-------------Charlie |
|
|
|
dbthj
Posting Yak Master
143 Posts |
Posted - 2008-08-19 : 12:23:01
|
| rmiao, There is 8 gig of memory on the box.Charlie, I looked at the article. It sounds a lot like a buffered i/o problem, though I am curious that most of the people having the problem are copying a file over the network between servers. And the suggestion is to buy a tool. My copy is local.KB259837 claims these problems were fixed in later releases of Windows 2000. Apparently, they came back in 2003 SP1.Another thread said,'Looking into it further it seems that PAE extensions are enabled by default on 2003 SP1 to support Hardware enforced DEP. As MS says "When the PAE kernel is used, the overhead is doubled and 4 KB of paged pool is required for each MB in the source file." which means that my maximum file would be ~50 GB which makes sense with what I'm seeing.'If this is true, then I need to check the size of the paged pool. Anybody know how to do that?I check MS doc on Windows 2003 SP2 and I see nothing about buffering or copy problems being addressed.dbthj |
|
|
|
dbthj
Posting Yak Master
143 Posts |
|
|
tripodal
Constraint Violating Yak Guru
259 Posts |
Posted - 2008-08-19 : 14:17:23
|
| Perhaps you can try winrar, shrink it down, move it over, expand itup?I <3 winrar. |
|
|
|
Transact Charlie
Master Smack Fu Yak Hacker
3451 Posts |
Posted - 2008-08-20 : 04:04:57
|
quote:
Perhaps you can try winrar, shrink it down, move it over, expand itup?I <3 winrar.
Great plan!Go with a compression engine and copy the compressed file instead!So simple it's genius.-------------Charlie |
|
|
|
dbthj
Posting Yak Master
143 Posts |
Posted - 2008-08-20 : 09:59:50
|
| I entertained the compress/rar idea. I've done that to ship backupsto vendors. I don't know why it wouldn't work with a .mdf but we don't have a dev box with lots of space to test it with. I get nervous crankingproprietary stuff through a black box that's going to mess with thecontents. Anybody tried this with a .mdf file? |
|
|
|
tripodal
Constraint Violating Yak Guru
259 Posts |
Posted - 2008-08-20 : 12:29:39
|
| Actually I have restored a Rar'd backup after downloading it through https. 4gb in size. shrunk it down to about 1gb. I would suggest using your managment workstation as the bastard child, rar it from the server to your workstation, and then unrar it from your workstation to the other server.You have the possibilty of leaving the rest of the server in production. Assuming your workstation cannot rar 12MB (10/100) or 120MB (gigabit) per second (my core2 3ghz is about 3mb) The network may not even notice it. |
|
|
|
|
Can't copy large .mdf file