A Fine Slice Of SQL Server
Robert Blackburn has a few tips for us:
Adding bigger or more nodes to your cluster increases costs. There are also diminishing returns. You do not need 64 cores if you are only using 10. But you still need a minimum that matches your processing requirements. If your utilization looks like this, you must increase the size of your cluster.
Click through for several good tips.
Comments closedSteve Jones shares some tooling recommendations:
It’s blog party week for T-SQL Tuesday, and I think this is a good choice for a topic. The host this month is Mikey Bronowski, and his invitation is on tools. I work for a tools vendor, and I’ve used a lot of them in my life, so I want to share what I think in 2021. I’ll also say that Mikey has a good list in his invitation of what he uses. I especially like his use of PoSh things and Greenshot.
I’ve going to tackle this in a couple ways as I really have two parts of my job here, so I’ll look at tech tools and then productivity tools.
Read on for Steve’s list.
Comments closedMatthew McGiffen looks at a common problem with statistics:
The Ascending Key Problem relates to the most recently inserted data in your table which is therefore also the data that may not have been sampled and included in the statistics histograms. This sort of issue is one of the reasons it can be critical to update your statistics more regularly than the built-in automatic thresholds.
We’ll look at the problem itself, but also some of the mitigations that you can take to deal with it within SQL Server.
Click through for more detail.
Comments closedJohn McCormack reviews several community tools for SQL Server:
Statistics Parser is a web page which allows you to paste in the statistics time,io output from the SSMS messages tab, and it formats into neat tables showing how much IO happens for each table. It is immediately easier to read and you get a handy % column on the right hand side showing you which tables are being read the most. I find this really useful for query tuning because it lets me know where my biggest pain points are. For complex queries, which touch a lot of tables, it just makes it easy to see at a glance where you should initially focus your attention. It also shows worktable and workfile tables which serves as a handy hint that tempdb is in play.
John lists a half-dozen but really drives in on Statistics Parser.
Comments closedEitan Blumin shares some recommendations of tools:
While I do feel that the tools that make my job the most awesome are those that help me with productivity, this month’s topic is a bit broader. Most of these, though, are widely known, so I’m not going to go into much detail about them.
Click through for Eitan’s suggestions. I use the majority of these (or at least some alternative) but there are some new and interesting ones for me.
2 Comments