With the lifecycle of SQL Server 2012 in full swing, many companies are looking to upgrade their 2008/2008 R2 instances in order to take advantage of what 2012 has to offer – especially now that SQL 2012 Service Pack 1 (SP1) has been released with its additional new BI specific features.
– Your CRM installation rollup requirement
- Rollup 6, for SQL 2012 RTM
- Rollup 10, for SQL 2012 SP1 (recommended)
– A full SQL Server 2012 Installation
- 64-bit only
- Enterprise, Business Intelligence, or Standard Edition
- SQL Reporting Services (SSRS) installed and deployed in Native Mode, with the Report Server URL handy.
– If CRM Reporting Extensions are installed
- Uninstall existing version on your CRM application server.
- Download and extract the CRM 2011 bits from here (these have updated bits that allow you to bypass an error some users have encountered) then run the setup program in the SrsDataConnector sub-folder.
Before moving your production instances over, you should make sure you can validate these tasks:
- Access both the SQL Reporting Services 2012 Report Manager and Report Server URLs as they are configured in Reporting Services Configuration Manager.
- In a SQL 2012 test environment, create a brand new organization.
- In a SQL 2012 test environment, import an existing organization from a production backup that is from a CRM 2011 instance running SQL 2008.
- Perform a basic smoke test of your environment, ensuring that basic functionality is working.
After successfully validating your test environments, planning for a production cutover should begin. Here is a basic Microsoft supported way of moving to a different database server – http://technet.microsoft.com/en-us/library/hh699772
Congratulations, you’re on SQL Server 2012 now!