Let me start by saying that this isn’t your typical post about the Halloween problem. This is intended to describe a couple different performance problems you should be keenly aware of.
Category: Administration
Why I don’t love SELECT INTO
Long ago there were locking / blocking problems with the SELECT INTO statement. That’s not the case anymore and for AdHoc operations and investigation of data SELECT INTO is very helpful.
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.
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.
An observation about Unicode in SQL Server Management Studio
A week or so ago I read a blog post and tweet about using an emoji in SQL Server. This inspired me to use the ninja cat emoji for my demo database name and something interesting was discovered.
A really simple bug with SSMS
If you’re a long time IT professional or an occasional user of high or even low tech software you’ll know what I mean when I say “Bugs are not a new thing”.
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.
Inside the mind of a c# developer
I’ve been working with SQL Server for 18 years and over that long span I’ve seen a lot of different techniques for tuning and development.
There are essentially two principles of development, Code First and Database First. Naturally, being a life long database professional I’d say that Database First is the only way to properly approach a project. You’d start with a business analyst gathering requirements, build out the database ERD, and then start coding.
