SQL Server Copy Database Wizard Error

Trying to use this method to move database from SQL 2008 to SQL 2016.    


The job fails and tells me to check the log file for details ... however no log file was created in the specified location.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You can simply create a backup of SQL 2008 database and restore it on SQL 2016. No Wizards are necessary.
Zoldy2000Author Commented:
I chose this method because it also supports copy jobs ... users ... etc...
Zoldy2000Author Commented:
if there is another way to copy my maintenance jobs over so I don't need to rebuild them then I could use your method
Need More Insight Into What’s Killing Your Network

Flow data analysis from SolarWinds NetFlow Traffic Analyzer (NTA), along with Network Performance Monitor (NPM), can give you deeper visibility into your network’s traffic.

First of all you should do these tasks manually which will teach you what everything is necessary to finalize the database port. Wizards does not allow to "look inside" and you then have no clue what everything can fail.

You can create a script for all your SQL jobs and execute it on the target machine. Of course, this requires users and logins defined on the target machine.
Zoldy2000Author Commented:
I understand what you are saying but at the same time for someone like me who manages one SQL server ... has maintenance plans and backups that were setup years ago and work as desired.    Copy is a much better option for me while Migrating to a new server.
Vitor MontalvãoMSSQL Senior EngineerCommented:
I wrote that article and happy that you're following it.
Since you're migrating from an old database version to a more recent one, you'll need to run the Wizard from the last version of SSMS, that perhaps you've installed in the target server. Are you doing that?
Btw, the logs can be checked through the SQL Server logs or through the Windows Event Viewer.
Zoldy2000Author Commented:
Yes I am running the wizard from the new server.
Vitor MontalvãoMSSQL Senior EngineerCommented:
Then you'll need to find the error message in the logs so we can help you further.
Oh, in my articles, exists a link to a MSDN article that shows how to import users from an old server.
For the SQL Agent jobs, you can just right-click on them and choose the option to Generate Scripts for each job. Then run the scripts in the new server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Zoldy2000Author Commented:
great thanks for the info .....    If i see those techniques to get the users and jobs then I could also just restore databases from backup.    this worked in my tests
Vitor MontalvãoMSSQL Senior EngineerCommented:
Yes, you can go for the others methods as Backup & Restore or Attach/Detach database.
Zoldy2000Author Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.