SharePoint database issue

We have a SharePoint 2013 farm and when it was created we setup the database server to a single node in a SQL 2012 cluster (ch1) and not to the cluster itself (sql2012).  We saw the error and added another database server to the SharePoint farm this time pointing to the SQL cluster.

We now have half the DB’s pointing to the single node and the other half pointing to the cluster.

The problem is when a node on the SQL cluster fails SharePoint is looking for the sql server on ch1 and fails.

The goal is to have all db’s point to sql2012 cluster.

 Looking for suggestions
•      Detach and reattach?
•      Alias the ch1 node?
•      hoping there is a powershell script
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I guess you have all the configuration databases on the node right?
The procedure is more or less similar to moving databases from one SQL to another.

The point may be, that in a cluster (and not only there) you should work with alias names for SQL, what makes moving really simple. If you used reals names, you may have to change the configuration of all service applications to point to the new sever name. What is some handwork.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vitor MontalvãoMSSQL Senior EngineerCommented:
Let me see if I understood.
You have a cluster with 2 nodes, where you installed in one single node a stand-alone MSSQL instance and a clustered MSSQL instance for both nodes?
If so, I recommend you to uninstall the stand-alone MSSQL instance and attach those databases in the clustered MSSQL instance.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.