Invitation and roundup from Russ Thomas.
This is your official invite to the SQL Server Performance Grand National. I want posts tackling “focused” performance tuning.
By “focused” I mean tackle something head on; the more secret sauce, tricks, code samples, operator costs, or demonstrable metrics against a defined problem the better. This month is for the gear heads. Don’t wimp out by avoiding hints, plans, or guides. General practice is for wusses. Write something that’ll either go BIG or flame out half-way down the track. Drag racers aren’t grocery getters. If your post begins with the phrase… should be implemented with caution – you’re doing it right. If you’re an SSIS, SSDT, SSRS person – we’ve got a funny car division for you too. Tell us edge cases where you’ve make your stuff scream.
Need some ideas?
- Tackle a non set based problem you’ve improved in the wild
- Discuss hardware settings or IO – anyone using a flash array?
- Got a solution to a niche wait type?
- Tackle indexing edges (good or bad)
- Columnstore !!!
- Hash buckets !!!
- Parallelism !!!
- Break down and improve a peculiar query plan operator
Invitation and Roundup from Robert Pearl.
So, let’s get this blog party started, and kick off our international Healthy SQL campaign. Let’s spread the word to anyone and everyone managing a SQL Server Database infrastructure of the necessity to perform regular health checks on each SQL Server and repeat often. The purpose here is to get database professionals, to ensure that all their SQL Servers are healthy, and can pass a health check. It also means that you can prove this (to heaven forbid, auditors), and back it up with documentation.
If you want to excel in your career as a data professional or DBA, then you need to be concerned about your companies’ SQLFitness. Therefore, I am inviting all of you, to blog about your T-SQL Resolution, and describe what it is that you will do this year to make sure your SQL Servers are healthy and fit. Now, it’s ok to ponder Healthy SQL in the abstract, but we’re looking for some technical tips on things a DBA should do to keep your SQL Servers performing well.
It could be something as simple as implementing a new monitoring software or script, updating all your SQL Servers to the latest version or service pack, setting up maintenance and optimization jobs, HA/DR, creating a performance baseline, capturing performance stats, (ie: DMV automation scripts, or MDW), a checklist ,etc. Sky is the limit, as long as you can contribute something to the SQLCommunity that can be used in the effort to ensure SQL Fitness.