1. Connections in Primary Role: change to Allow Read/Write connections.

2. Readable Secondary: change to Read-intent only

3. In the Availability Group settings under Read-Only Routing, check that you have set up...

As long as you don't wander off after BEGIN TRANSACTION and before COMMIT/ROLLBACK TRANSACTION and potentially cause an awful lot of blocking on that database :).

I don't know why, but this is default behaviour and not usually anything to worry about. There's no way to disable the message, unfortunately.

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/bc5c8a4b-bc09-4478-8434-7d2e0d5c203f/the-service-broker-endpoint-is-in-disabled-or-stopped-state?forum=sqlgetstarted

Could you definitely not just change the application connection string?

I hadn't spotted that there were more answers; thanks, all.

It might be something to do with how secondary replicas use RCSI. See what you think:

https://www.red-gate.com/simple-talk/sql/performance/read-committed-snapshot-isolation-high-version_ghost_record_count/

Increasingly, I don't think I do. I've never been very interested in coding. I can get by in Powershell and it impresses me what people can do with it, but...

You can put only one database into each AG if you like, I suppose. Why would you want to do this, out of interest?

Thanks. I've done some sampling, but I hoped there might be a broad rule I could use estate-wide. Never mind, at least I've had it confirmed.

I was going to say use an alias too, then you can just repoint it later if you need to.

No need to be rude, you hadn't specified that in your original post.

Is the cluster service running? It's under Services.

Do you mean they're not deleting from the Primary side? In the backup settings what do you have under "Delete Files Older Than"?

Having an admin account for the server doesn't necessarily mean you'll have access to the database instance. (Our Windows engineers don't, but they are obviously server admins.)

Regarding User Mapping, that's...

Finally, some sense!