Aaron Bertrand (@AaronBertrand) of SQL Sentry discusses a case where assumptions can lead to a poorly-performing query and where exploring other options can pay off.
Erin Stellato (@erinstellato) talks about the implications of holding onto data, beyond its reasonable lifetime, in monolithic, single-partition tables.
SQL Sentry's Aaron Bertrand (@AaronBertrand) reflects on the presentation he gave during the PASS Performance VC Summer Performance Palooza 2013 on June 27th, including a wealth of responses to Q & A.
SentryOne's Aaron Bertrand (@AaronBertrand) discusses a few additional places to get information useful for decisions about creating new indexes that are suggested as "missing" by various tools.
Aaron Bertrand (@AaronBertrand) of SQL Sentry discusses a couple of advantages and a hefty list of limitations with filtered indexes in SQL Server 2008 and above, with links to no less than 36 Connect items!
SQLskills' Joe Sack (@josephsack) walks us through an interesting scenario where we might blame a query performance issue on parameter sniffing or bad statistics, when it actually turns out that a check constraint is the best solution to keep the optimizer honest.
Jonathan Kehayias (@SQLPoolBoy) demonstrates column-side implicit conversions and the impact they can have on a workload. He concludes that you can only throw hardware at this problem for so long; a design or code change will be necessary to solve the performance issue long-term.
Erin Stellato (@erinstellato) of SQLskills.com tells us about statistics, sample size and the impact different choices can have on duration and subsequent queries.
Paul White (@SQL_Kiwi) makes some great points about limitations in SQL Server's optimizer, and things you need to watch out for, when it comes to filtered indexes.
Erin Stellato of SQLskills takes a deep look into the I/O impact of running DBCC CHECKCONSTRAINTS, including explaining why some check methods may consume a lot more I/O than others.
