Hello everybody,

I had a problem whith my sql migration server on sharepoint 2010.

My sharepoint use the sql OldSql\Instance1 on port 1497 ad i want to use
NewSql\Instance1 on port 1500 instead.

To do this as i see in many forums i use cliconfg enable tcp and in
configuration i fill the server alias by OldSql\Instance1 and server name by  NewSql

Furthermore in
regedit i change the dsn from

Data

Source=OldServer\Instance1,1497;Initial Catalog=SharePoint_Config;Integrated

Security=True;Enlist=False to Data

Source=NewServer\Instance1,1500;Initial Catalog=SharePoint_Config;Integrated

Security=True;Enlist=False

To finish in my OldSql\Instance1 i turned offline the database WssContent that
Sharepoint used to be sure that we use the NewOne which contains the same database
WssContent (its a copy) .

And there each time i tried i got an error as if my Sharepoint still pointed on
OldSql\Instance1.  Did i miss one step ? Is there any hidden Config String
?  Here are the log

0x1A7C Windows
SharePoint Services Database 880j High SqlError: 'Login failed for user
'EURO\svcmosscapp'.' Source: '.Net SqlClient Data Provider' Number: 18456
State: 1 Class: 14 Procedure: '' LineNumber: 65536 Server: OldServer\Instance1,1497'

0x1A7C Windows
SharePoint Services Database 6y63 Critical SQL Database 'WSS_Content_BNPP_ATP'
on SQL Server instance OldServer\Instance1,1497'
not found. Additional error information from SQL Server is included below.
Cannot open database "WSS_Content_BNPP_ATP" requested by the login.
The login failed. Login failed for user 'EURO\svcmosscapp'.

What you have tried is completely unsupported. 

You can never change the SQL server once sharepoint farm is created. You changed some setting on regedit but the setting still exiting in config DB which you cannot modify.

My suggestion would be to create old server alias on new server and continue refer old server alias as refereed 

below:

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=255

If you still wish to do it try following below:

https://technet.microsoft.com/en-us/library/cc512725.aspx

hello Indejeet thanks for your answer,

acutally i already made the same steps which i described on 4 others sharepoint server to change the sql server and it worked...

But it seems that this server had a different behaviour (Production environment) thats why i dont understand ...

Furthermore i can't create a old server alias on new server because the name are chosen by another team...

How can i change the settings since i already done all the things cliconfg etc etc... i really dont understand how sharepoint can point on the od server since i change all the things...

Hi,

Basically, the creation of a SQL alias on the SharePoint server, before the deployment, is a good practice.

If you did that, you just have to update the target server of the alias from old SQL server to new one.

If you didn't, I think you should do it rigth now. Use the old server name as alias name, and new server name as alias target.

Don't forget you'll have to do it twice :

once with %windir%\system32\cliconfg.exe

once with %windir%\sysWOW64\cliconfg.exe

Hope it helps

You only have to do it once with SharePoint, just Start -> Run -> cliconfig (which will launch the version in system32). SharePoint is an x64 application, so the 32bit cliconfig in SysWOW64 isn't leveraged.

It sounds like you need to update the connection for that particular content database. You could detach it from the Web Application, then use Mount-SPContentDatabase to add it back to 'update' the connection.

Trevor is right when saying SharePoint is 64bits, so 64bits alias is enough.
Simply, I think it can be weird to connect to different servers when using same name, depending what client I use, 32 or 64 bits; so I always recommand to create both aliases.

Cekamb, please let us know if you resolved your issue