Other than looking in DNS, is there any other ways to make sure nothing was pointing to the IP for the SQL side of things?

• This reply was modified 1 year, 10 months ago by  sqlguru.

Thanks Steve. Do the network team has to open up firewalls to listen the TCP port to the new IP address?

Any thoughts about extend on premises always on availability group to azure managed Instance

• This reply was modified 1 year, 10 months ago by  sqlguru.

I was referring to SQL 2017 Enterprise edition. It might be possible on azure vm node. But I am looking for Setup Alwayson with one node onprem and one azure...

So dedicated table needs to be created to capture the error handling? We do have third party monitoring but it didn't capture that particular proc as database activity.

Yes. That got captured in the batch log. Are you referring to logging and error handline something like TRY/CATCH blocks?

This is secondary read only replica which does not have SSRS installed. We use this replica for dedicated to reporting queries something like that. Sorry If I wasn't provide you...

Thanks. I agree with you. But this is read only copy used for reporting. We are looking for other ways to improve performance by adding more memory but also thinking...

I will be testing this.

Thanks. Another question my understanding is when the secondary database are on suspend mode the log on the primary will continue to grow as it hasn’t sent the data to...

Does data suspend in Always on AG will cause tempdb to grow as well or only Log growth?

I have checked and found that this application does not have that flexibility when there is DB changes that could stop the current version of application running. Any thoughts?

I am not sure how you can do that in AG. Have you tried with data suspend and resume? Are you getting any errors?

• This reply was modified 2 years, 3 months ago by  sqlguru.

Did you try Automatic seeding?

Read only routing will not work if the data movement suspended.