Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by Marios...
»
Preparing for the Unthinkable - a...
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Rate Topic
Display Mode
Topic Options
Author
Message
Marios Philippopoulos
Marios Philippopoulos
Posted Thursday, March 31, 2011 12:00 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 7:10 AM
Points: 1,824,
Visits: 3,477
Comments posted to this topic are about the item
Preparing for the Unthinkable - a Disaster/Recovery Implementation
__________________________________________________________________________________
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #1086627
dmfd
dmfd
Posted Thursday, March 31, 2011 7:12 PM
Forum Newbie
Group: General Forum Members
Last Login: Thursday, April 19, 2012 2:30 PM
Points: 5,
Visits: 14
Perfect 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.
Post #1087212
Marios Philippopoulos
Marios Philippopoulos
Posted Friday, April 01, 2011 7:10 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 7:10 AM
Points: 1,824,
Visits: 3,477
I'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.
__________________________________________________________________________________
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #1087436
dmfd
dmfd
Posted Friday, April 01, 2011 8:04 AM
Forum Newbie
Group: General Forum Members
Last Login: Thursday, April 19, 2012 2:30 PM
Points: 5,
Visits: 14
Thanks, I shall.
Post #1087482
JoeSchmoe007
JoeSchmoe007
Posted Thursday, December 13, 2012 11:30 AM
Forum Newbie
Group: General Forum Members
Last Login: Thursday, January 17, 2013 7:58 AM
Points: 2,
Visits: 116
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.
Post #1396332
Marios Philippopoulos
Marios Philippopoulos
Posted Friday, December 14, 2012 4:35 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 7:10 AM
Points: 1,824,
Visits: 3,477
JoeSchmoe007 (12/13/2012)
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?
__________________________________________________________________________________
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #1396582
JoeSchmoe007
JoeSchmoe007
Posted Friday, December 14, 2012 7:30 AM
Forum Newbie
Group: General Forum Members
Last Login: Thursday, January 17, 2013 7:58 AM
Points: 2,
Visits: 116
Marios Philippopoulos (12/14/2012)
JoeSchmoe007 (12/13/2012)
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?
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.
Post #1396655
Neha05
Neha05
Posted Monday, December 24, 2012 11:28 AM
SSC-Addicted
Group: General Forum Members
Last Login: Monday, April 15, 2013 11:42 PM
Points: 424,
Visits: 55
Thanks for sharing!
Post #1399943
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.