1 / 11

Managing a “0 Downtime” Shop

Chris Shaw:. Managing a “0 Downtime” Shop . Chris@SQLShaw.com http://chrisshaw.wordpress.com/. About Me. I am for hire…. 15 years as a DBA (Wells Fargo, Anthem, Yellow Pages, Pulte…) SQL Server MVP SSWUG Conference Chair(2008-2010), SQL Connections Track Chair (2008-2009)

shepry
Download Presentation

Managing a “0 Downtime” Shop

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chris Shaw: Managing a “0 Downtime” Shop Chris@SQLShaw.com http://chrisshaw.wordpress.com/

  2. About Me • I am for hire…. • 15 years as a DBA (Wells Fargo, Anthem, Yellow Pages, Pulte…) • SQL Server MVP • SSWUG Conference Chair(2008-2010), SQL Connections Track Chair (2008-2009) • Chris@sqlshaw.com • http://www.linkedin.com/in/christophershaw • Twitter - SQLShaw

  3. Session Pace • We have a long way to go and a short time to get there…. • Answers on my blog….. • If you want to talk more about something STOP me. • I may ask to take something offline. Find me after the session or at lunch • Scripts – on my blog

  4. Agenda • Challenges • What is really the most important? • Recoverability • Stability • Performance

  5. What are the Challenges are you seeing? • Bigger databases take longer to maintain. (Backups, Re-indexing, upgrades,… ) • Higher the availability the higher the price tag. (Disk space technology for a cluster is not going to be cheap) • Global Economy  Global Business/Customers  around the clock availability • Resources become harder to manage • SQL Server standard will become more challenging (table partitioning, database mirroring, backup compression, TDE) • Insufficient test environments (buy really cool hardware now do it twice) • Lack of head count • Growth Pains (fighting policies, technology debt) • Example…

  6. Now What? • Define what is really important and prioritize it. Here is my list. (This could be different for each of us) • Recoverability • Stability • Performance • What have I done now and in the past to make sure that the priority list is actually being addressed.

  7. Step One • Management database • Determine coverage times, how do you accommodate for odd hours • Third Party tools • Management companies • Hosting companies • What are the sore spots?

  8. Recoverability • Backups • Full Diff  T-Log • Compression • Third Party Products • File Groups • Retention Policies • Practice Restores • Plan your tests, and test your plans • Backup your staff

  9. Stability • Redundancy • High Availability • Role Segregation • Maintenance • Why DBCC • How do you re-index • DMV’s • Change Management • Security

  10. Performance • Monitoring • Database Design Creep • Recording your counters • Business measurements • Partitioned Tables\Partitioned Views • Your database to manage your database • Performance Indicators • Drive Space • Index fragmentation • Business counters

  11. Added Resources • Chris Shaw Blog - http://chrisshaw.wordpress.com/ • Glenn Berry - SQL Server Diag - http://glennberrysqlperformance.spaces.live.com/blog/cns!45041418ECCAA960!7086.entry • Paul Randal - HA with SQL Server 2008 White Paper – http://msdn.microsoft.com/en-us/library/ee523927.aspx • Features/editions SQL Server 2008 -http://msdn.microsoft.com/en-us/library/cc645993.aspx • SQL Server Central -http://www.sqlservercentral.com/articles/Disaster+Recovery/is0downtimepossible/600/ • Michelle Ufford- http://sqlfool.com/

More Related