New answers tagged sql-server
Keep your ALIAS as is. In your web.config change all your connection strings for your custom web-parts/apps to point to the IP address of the SQL server.
If you are able to identify which web.config settings should point to SQL1 and which should point to SQL2 then you should change the respective values to point to the correct alias (yes you can have both SQL1 and SQL2 aliases side-by-side pointing to different database servers). However, you can't route SQL traffic to a specific server from one alias. Think ...
As the change in the allocation should not require a SQL restart I would guess that you have something else hogging the rest of the RAM. Look into the Proccesses tab and see if the culprit is visible there. As a best practice, nothing except SQL should be running there.
I resolved the error by deleting the site collection in the new SharePoint 2013 farm and confirmed this by running Test-SPContentDatabase again. The orphan site error was no longer being reported.
It's very hard to know what actually happened during the process of renaming the SQL Server. Still, I will try to make a few suggestions of the steps that should have happened, but (from your post) didn't. Renaming a SQL Server with alias is close related to moving databases to another server with the same alias, but not actually moving anything. The ...
Top 50 recent answers are included