Assessing and Optimize Enterprise SQL Server Environments
summary
Enterprise-level audit shows most waste lives in a few places: top 1% of SQL code generates more than half the cost, and cost of code is measurable in dollars by mapping on‑prem servers to like‑for‑like cloud instances. Examples: a DBA utility table back to 2006 consumes 500 vCPUs; 30 redundant indexes on one table collapse to a single include and speed reports 45%; 22–30 warehouse copies can drive >50% of storage spend. Fortified Insights (Wisdom) is used to quantify and prioritize fixes.
AI-written summary · about
chapters (25)
- 0:00Enterprise SQL optimization intro
- 1:55Pareto principle for data platforms
- 3:01Innovation vs budget balance
- 6:15Cost impact of initial design
- 8:48Tech costs in business terms
- 9:52Top 10 queries optimization
- 11:37Runaway DBA utility DBs
- 14:07Low-risk config tweaks
- 17:00Cleaning redundant DB artifacts
- 18:25Data lifecycle management
- 19:52Fixing missing/excess indexes
- 22:01Non-prod env cost reduction
- 23:25Cost of code over time
- 24:26Fortified Wisdom cost demo
- 27:58Prioritize by financial impact
- 30:28True cost of data storage
- 33:21Avoid data hoarding
- 35:31Enterprise data strategy
- 36:32Reduce duplicate DB copies
- 37:59Reporting optimization wins
- 40:34Missing data strategy risks
- 41:381% rule for cost cuts
- 43:05Shift to cost efficiency
- 44:33Enforce dev cost budgets
- 45:38Q&A on platform cost
related talks
49mAssessing and Optimize Enterprise SQL Server Environments- 49mAssessing and Optimize Enterprise SQL Server Environments
44mTidy Space, Tidy Mind; How to Better Manage SQL Environments Across Cloud Providers
43mPerformance Tuning, Getting the Biggest Bang for Your Buck
31m10 Costly Database Performance Mistakes (and How to Fix Them)
18mHow to reduce your SQL Database costs on Azure
47mArchitecting for High Performance SQL Server on Virtual Machines
49mHow to Conduct a Transact-SQL Code Review