How I can to change status from SDS secondary to Primary.
rootdbs wanted to restore the original roles after a Connection Manager failover made the SDS secondary the primary and the old primary became an SDS secondary. Madison Pruet said to run onmode -d make primary on the old primary, but questioned why, since an SLA follows the current primary. He added that sqlhosts needs no change when using the Connection Manager.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hello All. I have my testing environment. I have server1 is primary server and server2 is SDS secondary server and one Connection Manager Arbitrator. When I shutdown my primary server, Connection Manager switches my application to the SDS secondary server. After that my server2 became is Primary. After restarting of server1 he became is SDS secondary. How I change a status of my servers to initial position. It might be without restarting my servers.
rootdbs@gmail.com wrote:
> Hello All.
> I have my testing environment.
> I have server1 is primary server and server2 is SDS secondary server
> and one Connection Manager Arbitrator.
> When I shutdown my primary server, Connection Manager switches my
> application to the SDS secondary server. After that my server2 became
> is Primary. After restarting of server1 he became is SDS secondary.
> How I change a status of my servers to initial position. It might be
> without restarting my servers.
run "onmode -d make primary <new primary>
In your case, the 'new primary' would actually be the old primary which
was made into the SDS.
Question --- why is it necessary to revert the server status? You are
using the connection manager, so you could configure an SLA to point to
the current primary.
> Question --- why is it necessary to revert the server status? You are > using the connection manager, so you could configure an SLA to point to > the current primary. I don’t think about it. But I think that not only SLA need configure. Sqlhosts on Connection manager host need to change string with primary server (may be I make mistake).
rootdbs@gmail.com wrote: >> Question --- why is it necessary to revert the server status? You are >> using the connection manager, so you could configure an SLA to point to >> the current primary. > > I don't think about it. > But I think that not only SLA need configure. Sqlhosts on Connection > manager host need to change string with primary server (may be I make > mistake). > > If you are using the connection manager, then you do not need to change the SQLHost file. The connection manager would redirect the client connection to the current primary node.