Hi,

Just wanted to check options here. We are migrating servers and it is a possibility that the content database name will be different for the new server. If I were to run the config wizard on the SharePoint front end server and insert the new content db name, does this change automatically propagate to service applications that have the content db name like the search service for example? Or do I have to manually re-create these service applications?

t

Not sure I would do it that way as that would probably create new content db's. Probably better to detach the database, change the name in SQL and then reattach the database. This should be seamless to the service applications.

Sorry, what I meant was that the SQL server name may be different. We will be still using the same content databases. And yes they will be detached and re-attached. 

Hi Sherazad,

After migrating SharePoint content databases to a new SQL server with a new name, we can create new SQL alias  on each SharePoint server to redirect the connections to the original, source SQL server to the new, target SQL server.

Please follow the steps in the link below to create the new alias on each SharePoint server:

http://www.codeproject.com/Articles/664029/Migrate-SharePoint-s-SQL-Server-to-another-SQL-Ser

Thanks,

Victoria