After deciding to take the leap of faith I considered my options as to what the safest way to upgrading my SharePoint site collection to SharePoint 2013 and upgrading my SSAS Database to SQL Server 2012.
I decided to create a new machine that had SharePoint 2013 and SQL Server 2012 fresh installations and to attempt to migrate my solution manually without the upgrade wizard.
this was done in the following order
Most of the steps were fairly simple and straight forward. After i had a stable environment i then began to migrate my solution starting with the site
Take backup of the site's content database and use the below command to restore it to SharePoint 2013
I decided to create a new machine that had SharePoint 2013 and SQL Server 2012 fresh installations and to attempt to migrate my solution manually without the upgrade wizard.
this was done in the following order
- Install SQL Server 2012 Enterprise (Database, SSAS in Multidimensional Mode, SSIS, SSRS)
- Install SharePoint 2013 Enterprise using the above database instance for hosting the config database
- Install SQL Server 2012 Enterprise PowerPivot and configure PowerPivot to create a new site collection
Most of the steps were fairly simple and straight forward. After i had a stable environment i then began to migrate my solution starting with the site
Take backup of the site's content database and use the below command to restore it to SharePoint 2013
Mount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" -WebApplication http://SiteName
After mounting the database upgrade it from the Central Admin. this should go pretty smoothly providing you don't have any custom code in your SharePoint site
i then proceeded to upgrade my SSIS packages and SSAS database which also went smoothly.
Then the first problem arose which is PerformancePoint could NOT connect to SSAS no matter which user i configured PerformancePoint with, after checking the logs i found this
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.AnalysisServices.AdomdClient, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
Basically this means that PerformancePoint is still using ADOMD v10 and not v11 which comes with SQL Server 2012 to try to connect. After installing ADOMD v10 from SQL Server 2008 R2 Feature Pack everything was finally working
