web connection string to database that are in Alwayson Availibility group

Question

web connection string to database that are in Alwayson Availibility group

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply

rivasol Newbie Points: 6 More actions · Answer 1

Thank you

organik gübre üretiminde kırmızı kaliforniya solucanı kullanılır. solucan gübresi üretimi için kullanılan kırmızı kaliforniya solucan fiyatı nedir? . en kaliteli solucan maması rivasolden alınır.
Bitkilerde, çiçeklerde, orkidede, sukulente solucan gübresi nasıl kullanılır. çiçeklerine iyi bakmak için solucan gübresi satın alıp bitkilerine iyi bakabilirsiniz. sıvı solucan gübresi ve katı solucan gübresi,

Ant-Green SSC Guru Points: 113507 More actions · Answer 2

Again Mirroring requires connection string changes to add in the FailoverPartner parameter.

Simply just changing a server to be "Server A" isn't just a simple thing in SQL and when invoking DR as you have to think about the fail back to primary when that comes back online.

So again, how much pain do you want to be in when your up against it, and this will then drive the discussion about what technology and solution would be best placed for you.

sqlfriend SSC Guru Points: 52781 More actions · Answer 3

Ant-Green wrote:

So again, how much pain do you want to be in when your up against it, and this will then drive the discussion about what technology and solution would be best placed for you.

In our case, it is just a connection string change in web.config file for the web application.

This reply was modified 2 years ago by sqlfriend.

Ant-Green SSC Guru Points: 113507 More actions · Answer 4

So do you need a listener is the question?

How many web.config files do you have to change?

What is your RTO?

What other servers/applications do you also need to look after in the event of a disaster and also have to make work in a DR situation?

If you only have this one SQL box and only have to change 1 web.config file well then yes you could get away without needing a listener and then change ServerA to ServerB in web.config when needed.

Now if you have to do this in 100s of places across 100s of servers and you need to do it in 60 minutes, well then you don’t want to be doing that in a disaster as you will make a mistake somewhere. So then you need a listener.

There are so many procedural questions along with technical questions which affect which solution you need to put in place and how things work when the situation arises.

So again, how much pain do YOU want to be in when management are pressuring you to fix the world and everything in it?

For me always very little, automate as much of it as you can, put a listener now at the configuration stage and change the web.config now to point to the listener. Save yourself the headache later on when things are down the drain as you will have bigger issues to think about then than changing a web.config file.