This article is useful. However, this approach will not work well for logins if Windows authentication is used for some logins and primary and DR servers are not a member of the same domain. In our case primary server is a member of domain and DR is not in a domain at all.
Thanks for sharing.
Yes, it's true that if prod and DR are not on the same domain, at least some of this functionality will break.
What are your contingency plans though if you end up having to use the DR in case of a disaster?
You would need to bring the DR into your prod domain, especially if applications are using Windows authentication in the prod environment.
If that is the case, why not include the DR in the production domain from now?
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]