July 28, 2002 at 2:13 pm
I seem to recall having problems with this wizard the last time I tried to use it. Whilst it did copy the database correctly it failed to keep auto incrementing identity column information. Has anyone else encountered this?
July 28, 2002 at 2:22 pm
I have not. There's no reason for it to happen that I can think of since you're moving the entire db as a file, not moving objects.
Andy
July 29, 2002 at 10:04 am
Andy: I do pass the point to select source and destination. The problem comes when it actually tries to execute. It says "Cannot create share ...". As I said the rights should be sufficient for the SQL account and SQLAgent account.
July 29, 2002 at 10:54 am
Definitely have to determine why you can't create the share. Did my testing on a single machine, will have to see about a cross server test.
Andy
September 23, 2002 at 4:55 am
The article is quite useful. My interest in using CDW was I'm not a SQL man and I just wanted a simple way to move SLQ 7 Dbs to a more high spec'd SQL 2000 standard edition. Trouble is every get copied across except for the actual data files (mdf & ldf). The copy process fails every time with very little info as to why and I cant figure it out. Any ideas?
September 23, 2002 at 5:07 am
Have you expanded the info you get at the end? That usually shows something. If not one time only try to replicate the sequence. Detach the db, copy to new server, reattach to orig, attach to new. Pretty common issue is disk permissions for the copy.
Andy
July 28, 2003 at 8:05 am
Hello Andy,
I found your article very userful. However, when I followed all the steps and DTS package was created on destination server, it never executed and I had to manually execute it. Is there a reason for that? Also DB never populated on destination server. How do I know that what was the problem? Was there a problem copying the DB? I would appreciate your comments.
Ahsan.
January 7, 2004 at 8:57 am
I found the article to be very usefull and quite insightful. I think that a discussion or reference to how one might reattach the databases after the copy has completed would be useful.
(I say that predominantly because my databases are defunct on the original server after having moved them. I know that the datafiles are still there but the wizard did not reattach them after the copy procedure and I was looking for an easy way of doing that)
August 10, 2006 at 4:09 pm
This fails at my installation copying from server to server. It fails at the copy step because it is using UNC. An example would be \\SqlServer01\test\test_data.mdf instead of using E:\test\test_data.mdf. Any suggestions. Everything looks good in the log up until the copy starts and then it fails and reattachs the database. Using MSDE 2000 SP4.
Thanks
Mark
Viewing 9 posts - 16 through 23 (of 23 total)
You must be logged in to reply to this topic. Login to reply