best way to upgrade

Hi,

I have a few db in sql 2008. I want to migrate them to sql 2014.  Other than backup and restore, any other steps I need to pay attention to? thx
mcrmgAsked:
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.

Pawan KumarDatabase ExpertCommented:
Few things you need to verify-

1. OS > 2008.
2. Bit should be same , if current in 32 bit then it will be upgraded to 32 only not 64.
3. You will need to handle important server level objects, migration will only db level objects.
4. Also note that you cannot go back from 2014 to 2008. Lets say you moved to 2014 and after 2 months you wanted to go back.
5. Are they live Dbs then you may need to decide the process like mirroring/log shipping etc to migrate.
6. Do not change settings after migration like database compatibility level

Also read - https://msdn.microsoft.com/en-us/library/mt551979.aspx

Hope it helps.
0

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
arnoldCommented:
Other than the sql anything else us being upgraded?

The upgrade path us a one way process, should issues cone up such as the application that uses the data can not interact with SQL 2014 because the means by which it interacts with SQL is that it uses an older SQL native client library (from SQL 2005)

Presumably you verified in a test environment that your application works with the data being on SQL 2014.

At times, installing the SQL native client library for SQL 2012,8,14   Could provide a transition i.e. If it uses an odbc DSN which merely require you to adjust the existing to use a different SQL native cli.
Testing is the most important part when doing an upgrade. If you can transition to another system such that you can fall back if an issue is discovered, i'de suggest that us a safer path.

Depending on available resources, storage, ram and size of db, to do a side by side, two SQL servers
With data paths in different locations,
Add another ip to the system and bind the SQL 2014 default /similar instance as the SQL 2008 to this new ip.

Down time, Backup on SQL 2008, restore on SQL 2014 after transferring sql logins, repoint the application to the 2014 SQL instance, and test it out during the down time, all go, leave as is, and go through the process to Devon the SQL 2008 instance, transfer any jobs, TDs packages, etc.
Once it is running .... Note the longer it runs before some rare task is executed and fails, you would need to go through the application to fix as there is no way to transition back to SQL 2008.
0
mcrmgAuthor Commented:
thank you very much
0
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.