Обновление sql 2005 до 2012 инструкция пошаговая

• Remove From My Forums

All replies

• User77042963 posted

  Go ahead and just do it. It should work.

• User1967761114 posted

  Hi kashifdotnet,

  According to your description, at first, you could understand the compatibility level with SQL server, see the following table.

                                    Compatibility level

  SQL Server 2000          80

  SQL Server 2005          90

  SQL Server 2008         100

  SQL Server 2012         110

  You could change the compatibility level by the following statements

  ALTER DATABASE [DBName] SET COMPATIBILITY_LEVEL = 110;

  In your case, the database is in 2005(compatibility level=90), when you restore to 2012
  there has no problem because of the SQL Server is backward compatible, 

  For more details about how to backup and restore database, you could refer to the following link.

  https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases

  If you have any other questions, please feel free to contact me any time.

  Best Regards

  Even

• User77042963 posted

  Hi kashifdotnet,

  According to your description, at first, you could understand the compatibility level with SQL server, see the following table.

                                    Compatibility level

  SQL Server 2000          80

  SQL Server 2005          90

  SQL Server 2008         100

  SQL Server 2012         110

  You unnecessary to change the compatibility level by manually, it will auto changed when you restore database.

  In your case, the database is in 2005(compatibility level=90), when you restore to 2012(SQL Server is backward compatible), the compatibility level will auto changed to 110.

  Are these statements are true? I remember that the restored database holds their old compatibility level property.

• User1967761114 posted

  Hi limno,

  Sorry, I had been modified my answer, thanks for you to indicate my error.

  Best Regards

  Even

• User77042963 posted

  Hi limno,

  Sorry, I had been modified my answer, thanks for you to indicate my error.

  Best Regards

  Even

  You are welcome.

• User197122282 posted

  EvenMa, Limno, thanks for replying. Many sites suggest running the
  SQL Server Upgrade Adviser before an upgrade. For me, the adviser came back with the following two issues:

  1. Full-text Search has changed since SQL Server 2008

  2. After upgrade, compatibility level 60, 65… will be set to 90 (90 obviously remains at 90)

  If I am not mistaken, non of the above is a real issue. My only concern is that after the upgrade, if I change the compatibility level to 110 (to take advantage of newer features), is that going to affect the database in any way.

  Further, many sites talk about ‘after running the SQL Server Upgrade Adviser,
  perform the upgrade‘. As far as I know, there are 2 possible ways to upgrade a database including 1) Backup and Restore 2) Detach and Attach. Does the upgrade process refer to something different?

  One more question. What are the features available in CL 110 but not available in CL 90.

  Thanks all.

Answers

• I would probably make a clean installation of SQL Server Express 2012 and keep SQL Server 2005 Express installed for now. Only once you installed the 2012 version, migrated your databases, re-pointed your applications and make sure all is working correctly,
  then you may uninstall 2005 version.

  ---

  • Marked as answer by

    Wednesday, September 2, 2015 12:02 AM

• In General please follow the below steps before starting migration….  and decide which method are you going to use… inplace or side by side…

  http://blogs.technet.com/b/francesco_diaz/archive/2008/12/16/in-place-vs-side-by-side-upgrade.aspx

  1. Run upgrade adviser on the databases for the instance you want to upgrade.
  2. If any issues are found, talk to your dev team/ Vendor for fixing the same.
  3. If issues are fixed proceed with the actual upgrade. — Do check for the other dependencies on the database which might effect the functionality if the instance gets upgraded or something like that.
  4. Get the downtime for the database.
  5. Create the latest full backup of the database — any other strategy will also work, just make sure you can recover the database.
  6. Take a clone of the server if it’s a virtual server to roll back any changes.
  7. Run the upgrade on the sql 2005 instance from the 2012 set up. — do check the pre-requirements for upgrade to sql 2012.
  8. If everything is fine then you have an upgraded instance.
  9. Also check the compatibility of the databases.
  10. If all is fine then congrats you have upgraded your sql server instance.

  Supported versions :—

  did you checked your sql 2005 service pack ?

  SQL Server 2012 supports upgrade from the following versions of SQL Server:

  • SQL Server 2005 SP4 or later

  • SQL Server 2008 SP2 or later

  • SQL Server 2008 R2 SP1 or later

  https://technet.microsoft.com/en-us/library/ms143393%28v=sql.110%29.aspx

  ---

  Raju Rasagounder Sr MSSQL DBA

  • Marked as answer by
    MyGposts
    Wednesday, September 2, 2015 12:01 AM

1