Backup and restore MSSQL DB

Hi , what is the step to backup from MSSQL express to the MSSQL SQL 12
Julio JoseAsked:
Who is Participating?
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.

This link: Back Up and Restore of SQL Server Databases

... has the latest version of all the backup information. How-to examples are at the bottom of the page.

* Not sure this applies to Express:
 Basically you can right-click on the [database name]  > Tasks > Back Up ... in SSMS, run a full backup to a disk 'device'. Leave the default folder location, append the file name (i.e. myBackup.bak) and make a note of it.

It's likely easiest to copy the backup file to the MSSQL folder (or new subfolder thereof ) on the destination server (i.e. C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\). You should be able to right-click on the 'Databases' folder > Restore Database ... in SSMS.

The link has pretty much all you need to know to do every type of back up and restore. I encourage you to read all of that material sometime, however it is not required for the task at hand.

Examples for back up and restore via SQL command are also available in that link.

Good luck!
Julio JoseAuthor Commented:
receive error when I try backup

Do you get the same error using this T-SQL command?
TO DISK = 'C:\JulioPath\dbJulio.BAK'

Open in new window

where "dbJulio" is the name of your database and "C:\JulioPath\" is where you want to put the backup.

If so, as you seem to be attempting to migrate from SQL Server Express 2012 to Enterprise 2014, I believe (I haven't tried it!) that it would be possible to simply detach the database from the Express server (using SSMS) and attach it to the Enterprise one using SSMS - possibly with a file copy in between to get it to the right place. Once you have done that then you could move data between databases using the SSMS tools.

Finally, if all else fails, try creating an equivalent database on the enterprise server. Then use SSIS to move the data from the 2012 database to the new 2014 one.

Hope this helps

Learn Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

Good tips, Mike!

Another one would be to Script Database As ... to replicate the database structure. Perhaps that's what Mike meant by "try creating an equivalent database on the enterprise server".
Nakul VachhrajaniTechnical Architect, Capgemini IndiaCommented:
Backing up and restoring from SQL 2012 to SQL 2014 should not be a problem. Based on the screenshots, it looks like you are trying to use SSMS for SQL 2008 - which will result in the Index out of bounds message.

Try to use SSMS for SQL 2012 for backup and SSMS for SQL 2014 for the restore. If those are not available, using the BACKUP DATABASE T-SQL command is your best bet.

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
Vitor MontalvãoMSSQL Senior EngineerCommented:
receive error when I try backup
What's the error?
Julio JoseAuthor Commented:
Follow Rakul step use the same version SMS, I can backup and successful restore the DB on the new DB server.

However when the application try to connect, I get this error from sql log, this is the same application user attempt to connect I can see the user include successful restore, how do I perform password reset for this user
Vitor MontalvãoMSSQL Senior EngineerCommented:
When you restore a backup in a different SQL Server instance you need to guarantee that the same login exists in the target SQL Server instance. If not then you need to create it and match the login with the desired user.
Here's the Microsoft's article about transferring SQL Server logins.
Julio JoseAuthor Commented:
why sound so complicated? I need step for SQL express 2012 to SQL Server 2014, the version not listed support on the MS site.
Vitor MontalvãoMSSQL Senior EngineerCommented:
You're only migrating a database and that's nothing complicated with that. A SQL Server Express database has no difference from any other regular SQL Server edition. The limitation is only handled by the engine and not the database itself.

I wrote 3 articles about SQL Server database migration. Each one with a different method but the goal is the same. Have a read on them so I think it will help you knowing more about the process:
SQL Server database migration - The Detach/Attach method
SQL Server database migration - The Backup & Restore method
SQL Server database migration - The Copy Database Wizard method
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
Microsoft SQL Server

From novice to tech pro — start learning today.