Welcome to the world (new face) of Knowledge Sharing Network.
To track the older blog posts refer to our historical knowledge sharing site  and you will find this as your destination for SQL Server knowledge pool.

Follow SQLMaster on Twitter SqlServer-QA.net - Knowledge Sharing Network (@sqlmaster)

Achieve SQL Server 2008 High Availability and Disaster Recovery - technical case study, SQLBits - SQL Server Knowledge Sharing Network (@sqlmaster)

Achieve SQL Server 2008 High Availability and Disaster Recovery - technical case study, SQLBits

How can you achieve the High Availability & Disaster Recovery  on database platform?

What are factors involved to keep the system available to maintain revenue stream?

What kind of management principles you need to implement?

Well there are lot more questions involved to the subject, only few important that I have listed above and in this regard on the topic agenda I'm speaking in a major SQL Server User conference in UK on 20th November 2009 - SQLBits V register here if you haven't done yet!

There is an in-depth on the subject to achieve maximum throughput for data, and also you should eliminate all single points of failure in architecture, and developed procedures for patching servers, upgrading software, and implementing application changes that preserve high availability. Based on these efforts, you can achieve 99.99 percent uptime, including both planned and unplanned downtime.

The session will highlight the important decisions and procedures that are employed to maintain maximum availability with minimal downtime. We will also cover the design of a 'achieveable' high-availability strategy by understanding all the requirements the strategy needs to meet. Lets not forget the limitations of technology and little compromise on evaluation of factors within platform, application and also consider the list of requirements that must be used when choosing which technologies to use.

No doubt that SQL Server 2008 provides all the technologies needed to implement a high-availability strategy, but knowing you have implemented a successful high-availability strategy relies on testing the system against failures—it is far better to simulate a failure with all staff on hand to aid with recovery than to experience a failure when no one expects it and end up with more downtime and data loss than necessary.

This information will be of interest to senior IT managers, project leads, architects, and database administrators (DBAs). All the content is presented from my own experience and industry best practices with a tour of Microsoft methods, it will sum up a great deal of procedures to achieve high availability and disaster recovery.

See you there!


Published Wednesday, November 11, 2009 4:57 PM by ssqa.net


No Comments