I wanted to take a quick moment to thank Denny Cherry for selecting me for Speaker Idol this year.
Category: Performance
Read this before using SQL 2016 Temporal Tables
I’ve been testing the new Temporal Tables feature over the past day to see about using it in one of our production databases. It’s a neat feature that honestly adds a boat load of possibility around logging.
In my testing I noticed that user created tables seem to store the rows over quite a bit more pages. User created history tables were nearly double the size of an auto generated one. If you’re currently using the feature or plan to use it in the near future, you’ll want to think about this storage issue before you implement.
A quick note comparing ISNULL vs COALESCE
There are hundreds of blogs that compare the T-SQL ISNULL function with the ANSI standard COALESCE function. There are also plenty of arguments of why you should use one over the other.
Understanding the new MAXDOP settings in SQL 2016
If you have just begun using SQL Server 2016 or you have been using it for a while now you may not have noticed the new MAXDOP settings.
Splitting CSV strings in SQL 2016
Up until SQL Server 2016, we had to write our own functions to split a CSV string into a table list. This was accomplished by writing a table value user defined function.
Join me and Kalen Delaney today for 24HOP
I’m excited to be monitoring Kalen’s session on concurrency. The session is today and is titled “Locking, Blocking, Versions: Concurrency for Maximum Performance”.Read More »
When should I use a CTE?
If I had a dollar for every CTE solution to a simple query in the forums (pick any SQL forum), I’d be Mark Cuban. With that said I thought it would be a good idea to ask if a CTE was actually the right solution or if it’s just the new trend and everyone uses them just because they can and all the cool kids are too. Let’s put it this way: If I had a dollar for every time a CTE was misused, I’d be Mark Cuban… or at least Robert Herjavec.
I’m speaking at SQL Saturday 563 in Dallas
This will be my second time speaking at SQL Saturday in Dallas. My first was last year and it was a great time. I enjoyed hanging out with all the attendees and speakers. Who wouldn’t want to have a chat with Kalen Delaney or Bob Ward? The Dallas edition of SQL Saturday is on 9/24 in Arlington at the University of Texas. Be sure to set the date I’m sure this will be a lot of fun and there will be plenty to learn!
My session is A DBA’s guide to whole stack performance troubleshooting. You’ll want to check this out.
You can register for this free event here: http://www.sqlsaturday.com/563/eventhome.aspx
Also, be sure to follow me on Twitter (@SQLSME) and on LinkedIn!
I’m speaking at SQL Saturday 553 in Oklahoma City
This will be my first time speaking in Oklahoma on 8/27 in Oklahoma City. I’ve been to several customers there but have yet to meet people from the users groups.
My session is Analyze your query plan like a Microsoft Engineer! (SQL 2016 Edition). If you deal with tuning, monitoring, or developing queries for SQL Server, you’ll want to check this out.
You can register for this free event here: http://www.sqlsaturday.com/553/eventhome.aspx
Using PowerShell to find Processor issues & more
One of the top three performance killers for SQL Server is lack of processing power. I’d say that it’s second only to storage latency and more of a concern than memory. Although with anything in SQL we can say it depends.
