Manage sql server proactively
Download as PPTX, PDF1 like445 views
The document discusses how to manage SQL Server proactively by understanding the present state including configuration, performance baselines, and service level agreements; investing for the future such as backup strategies, maintenance plans, monitoring and alerts; and not ignoring the past such as continuous monitoring and log retention to address issues quickly. It encourages attendees to share tools that fall under proactively managing SQL Server for present, future and past states.
Manage sql server proactively
- 1. 1 SQL Server – Manage SQL Server Proactively Enhancing SQL Server Performance with Columnstore Index Harsh Chawla Premier Field Engineer – Microsoft Services
- 2. About Me Harsh Chawla Premier Field Engineer, India More than 7 years with Microsoft and overall 9 years of experience Formerly with SQL Server CSS support engineering team Technology expertise: SQL Server Highlights: • Presented in TechEd Bangalore , 2014 • Consistently delivering proactive/reactive services to Indian market • SME on Performance and Tuning and SQL Azure solutions • Running SQL Community in Delhi for last 10 months Personal Blog : http://dbcouncil.net Twitter : @Harsh_Chawla1 FB Group – SQL Server Community Delhi NCR FB Page - DBCouncil
- 5. 5 Three Basic Principles Understand your “Present” Invest for better “Future” Don’t Ignore “Past”
- 6. 6 Understand your Present Understand the Business impact of the application hosted on your SQL Server instance SLA of the application SQL Configuration – Instance level and Database Level Disk Configuration – Know RAID Levels / IOPS Disk layout for the databases RTO and RPO SQL Server Instance Baselining (CPU/Memory/IO/Batches/Transactions) What else?
- 7. 7 Invest for better “Future” Backup Strategy (RPO and RTO) Consistency checks Database maintenance (Rebuild Indexes , Update Statistics) Database Security Database Monitoring Alerts Build Index Strategy (Scheduled tasks for DBAs to find missing/duplicate/tables without indexes etc.) Set up right SQL server configuration e.g. SP_configure/tempdb/SQL Databases What else?
- 8. 8 Don’t ignore “Past” Setup continuous monitoring using SCOM/Perfmon/MDW Have retention policy for Error logs/Agent logs / Event logs Setup Auditing What else?
- 9. 9 What will be your first step on Monday?
- 10. 10 Q & A Share the various tools which fall under these three categories
Editor's Notes
- #4: Got a call from the customer to help them for critsit issue --CPU was 100% and memory was touching the roof and Same with IO --He told we have brand new hardware it’s Tier 2 SAN from Some vendor and I have octa core processors Do you generally see performance issues ? Yes we do, But we kill the SQL sessions or sometimes restart SQL server early morning – SQL runs smooth through out the day. This time we forgot to restart and we saw a downtime during peak business hours 1. Bring them out of the situation and talk about the scenario of a patient 2. And then try to ask them the questions on how they could have avoided the illness 3. Why do they say – Full body health checkup monthly once
- #8: Benchmarking Monitoring Know your present Make your future better