April 8, 2010 at 4:25 am
April 8, 2010 at 4:55 am
I would go with Mirroring
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
April 8, 2010 at 5:44 am
What is your goal with this/these DRP ?
Microsoft SQL Server 2005 has a number of ways that can help you.
- Failover Cluster (shared storage)
- Database Mirroring
- Database Replication
- Log Shipping.
- database snapshots
Any which way you choose .... you still need a solid backup/recovery plan for your databases and instances !
Books online has a good overview: topic "Configuring High Availability "
You can find good resources at Technet:
- http://technet.microsoft.com/en-us/magazine/2007.03.highavailability.aspx
- Database Mirroring Best Practices and Performance Considerations http://download.microsoft.com/download/4/7/a/47a548b9-249e-484c-abd7-29f31282b04d/DBM_Best_Pract.doc
---> dbmirroring is advised only for up to 10 database ! See topic "Mirroring Multiple Databases"
This is a starter with sql2008 : http://msdn.microsoft.com/en-us/library/ms190202.aspx
Which may also give you a good impression for your sql2005 options or even chose for sql2008 in the first place.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
April 13, 2010 at 12:09 am
Hello,
Thanks for the reply.
But My question still remains the same :-
Suppose you have a SQL Server Instance which has more than 80+ User Databases and we need to paln the DR for this particular instance then what will be the best approach with Minimum Administrative efforts.
Log Shipping :- We will require to monitor more than 240 Jobs....
So is there any Solution where in we can Setup Log Shipping for an SQL Server Instance level rather than the Database level....
April 13, 2010 at 12:53 am
The question is also the same ...
Is your goal High availability and/or Data loss protection ?
Do you want no application modification impact (connection string) ?
Do you want no application modification impact (connection string) at fail time ?
How many second/minutes/hours can you afford to be down / offline ?
What kind of data loss can you allow at fail time ?
What kind of network is involved (lan/wan) with which bandwidth ?
What's the physical distance between your sites ?
Are you planing an active/active solution or a active/passive solution ?
With a hot stand-by ?
And ... just as a little sidenote ... how many $$$ are you planning to spend on this solution ?
Did you consider using the cloud ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
April 19, 2010 at 3:03 am
You need to start with what the business expects. This may be different for different databases. Different expectations will drive different solutions.
Take a look at the questions given by ALZDBA and try to categorise your databases according to those questions. This should give you one or more availability targets. You can then look at the best solution for each target.
If you as a technical team member implement a DR solution without respecting what the business expects and is willing to pay for, you will get no thanks.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 20, 2010 at 3:12 am
Any DR solution directly depends on the following.
• Amount data loss that is affordable.
• Maximum downtime of database that is affordable.
• Budget allotted to accomplish this task
Considering above you should be deciding which DR solution suite your databases better.
Thanks
Samji
- SAMJI
If you marry one they will fight with you, If you marry 2 they will fight for you 🙂
April 21, 2010 at 7:17 am
If I had to vote now, I'd go with mirroring. I'm worried log shipping would get bogged down with 80+ databases...but thats just a guess. But like earlier people said....have a solid backup plan and get the business people to buy in.
April 21, 2010 at 9:02 am
What edition/version of SQL Server are you running?
It's worth noting that Standard Edition only supports synchronous mirroring; if you want asynch, you need Enterprise Edition. It's also worth noting that the 32-bit editions can only mirror approximately 10 databases. Depending on what you're running, this may make your decision for you.
BOL reference for 10-DB limit on 32-bit versions
Good article on mirroring capacity from SQL CAT
Good KB article (written by Paul Randal) on mirroring considerations
______
Twitter: @Control_Group
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply