InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 26 May 2013 01:59:41 GMT20http://www.sqlservercentral.com/Forums/Topic1086627-1399-1.aspxThanks for sharing!Mon, 24 Dec 2012 11:28:19 GMTNeha05http://www.sqlservercentral.com/Forums/Topic1086627-1399-1.aspx[quote][b]Marios Philippopoulos (12/14/2012)[/b][hr][quote][b]JoeSchmoe007 (12/13/2012)[/b][hr]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.[/quote]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?[/quote]Ideally we should but we only have one computer in DR location at this time and no permanent VPN connection to primary site, so it is not possible.Fri, 14 Dec 2012 07:30:39 GMTJoeSchmoe007http://www.sqlservercentral.com/Forums/Topic1086627-1399-1.aspx[quote][b]JoeSchmoe007 (12/13/2012)[/b][hr]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.[/quote]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?Fri, 14 Dec 2012 04:35:39 GMTMarios Philippopouloshttp://www.sqlservercentral.com/Forums/Topic1086627-1399-1.aspxThis 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.Thu, 13 Dec 2012 11:30:24 GMTJoeSchmoe007http://www.sqlservercentral.com/Forums/Topic1086627-1399-1.aspxThanks, I shall.Fri, 01 Apr 2011 08:04:02 GMTdmfdhttp://www.sqlservercentral.com/Forums/Topic1086627-1399-1.aspxI'm glad this is of potential use to you. Go ahead and download the code, deploy it and please let me know of any bugs or anything I may have missed.I have tested this code repeatedly, but you never know what I may have missed. ;-)Fri, 01 Apr 2011 07:10:54 GMTMarios Philippopouloshttp://www.sqlservercentral.com/Forums/Topic1086627-1399-1.aspxPerfect timing on your article. I am currently at a start up and we are working furiously to get the database operationally ready. D/R has been in the back of my mind for weeks, and now is the perfect time to move on this before we have actual production data at risk. Thanks. :-DThu, 31 Mar 2011 19:12:55 GMTdmfdhttp://www.sqlservercentral.com/Forums/Topic1086627-1399-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/Disaster+Recovery+(DR)/71992/">Preparing for the Unthinkable - a Disaster/Recovery Implementation</A>[/B]Thu, 31 Mar 2011 00:00:58 GMTMarios Philippopoulos