I recently worked on a project for fraud. This project needed to relate 67 million accounts to one another “Kevin Bacon” style. This means that each unique account may tie to another account on ssn, email, home phone, business phone, or any other PII type metric.
I was building out a blog post about cardinality today and noticed that sys.dm_exec_query_stats was getting cleared my my Surface Pro 3 dev instance about every 30 to 60 seconds.
I opened object explorer to check if any jobs were running in SQL Agent that may be running DBCC FREEPROCCACHE
If you’re a DBA or a developer chances are you’ve looked at a query plan or two. While looking at your plan you may have noticed that each operator has a cost. Did you know that the cost is measurable?
If you’re a DBA or database developer, chances are you will have to write or rewrite queries from time to time. Rewriting may be for new features or simply to improve the performance of existing code.
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.
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.
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.
Has SSMS (SQL Server Management Studio) been crashing on you? Have you been getting Out of Memory messages when attempting to run queries?
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”.
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