Contents
Are there any issues with upgrading SQL Server?
The second instance – which hosts the SharePoint databases and Reporting Services – had a strange issue during setup. After downloading and extracting the CU file, we launched the upgrade process by double clicking the .exe file.
Why is MY SQL Server performance so bad?
However, there have been few scenarios when the upgrade happens the performance is poor. There can be multiple reasons why your performance may be bad after upgrading to the latest version and it is not possible to discuss them without doing a proper investigation of SQL Server.
How does the database compatibility level affect performance?
Since SQL Server 2014, the database compatibility level affects the default cardinality estimator that the query optimizer will use. Since SQL Server 2016, the database compatibility level also controls other performance related behavior by default. I have written more about this subject here:
What was the exception thrown when upgrading SQL Server?
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91.
How to upgrade SQL Server 2012 Service Pack 1?
The blog post suggests to reset the .NET security policy using caspol.exe with the following command: And indeed, after issuing this command against the different .NET frameworks on the system, setup started without a problem and the upgrade finished successfully!
Are there any issues with SQL Server 2012?
Additional exception information: Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91. Could not load file or assembly ‘Microsoft.AnalysisServices.SPClient, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies.
Can you open default instance of SQL Server 2008?
I can open default instance both from SQL Server 2008 and 2012. Also I have updated the compatibility level of all databases to 110. SSMS is just a tool to connect to SQL Server. You did an inplace upgrade, but were connecting to SQL Server 2012 using SSMS 2008R2 and SSMS 2012.