March 27, 2019 at 4:19 pm
Copy database is failing with time out expired. Is there a way to increase the time out period for copy database to different server? The db size is 15GB. I know the recommended size to copy database should be use for less than 500MB. I am sure backup/Restore would be the best option. Just curious any thoughts?
March 27, 2019 at 10:44 pm
Some people have encountered timeouts with DBs over 1 GB during the CREATE DATABASE phase and got around it by creating an empty database first on the destination. Do you have the full error stack from the timeout? That might help narrow down where the issue is.
On a side note, why do you want to copy the database using the Copy Database Wizard?
I ask because backup and restore, detach and attach or creating a DACPAC using Export Database are alternative options that may suit your requirements better and you have more control over the process to avoid or resolve issues like this. In addition, these options can be automated through scripting or SQL Agent jobs if there is an ongoing requirement for this copy.
These options might work better than the Copy Database Wizard (though I think from memory Copy Database can also use Detach/Attach method). Which option is best depends on your requirements.
March 28, 2019 at 4:08 am
Hi,
please check, if IFI is active.
If not, the 15 GB will be written with "0",
Kind regards,
Andreas
March 28, 2019 at 5:46 pm
andreas.kreuzberg - Thursday, March 28, 2019 4:08 AMHi,
please check, if IFI is active.
If not, the 15 GB will be written with "0",
Kind regards,
Andreas
Unless it is a large log file, which doesn't get the IFI improvement, log files are always zeroed.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply