I'm Back!
I've been gone... wow. Since March 31st of this year?! Let's fix that.
So what has been holding me back?
Kids? I...
2016-09-23
369 reads
I've been gone... wow. Since March 31st of this year?! Let's fix that.
So what has been holding me back?
Kids? I...
2016-09-23
369 reads
Warning: This is a really short post.
Today March 31st, BrentOzar.com is giving away their videos! Well, not giving away... but...
2016-03-31
751 reads
We're proud to bring back the OKC SQL Saturday for the 5th year in a row! We have 3 precons...
2015-03-09
755 reads
I've been gone for a bit, forgive the long delay. Who would have thought the hatred for a cascading delete...
2015-03-03
1,070 reads
This is just a short update. I will be speaking at SQL Saturday Kansas City! I really hope to see...
2014-09-08
581 reads
SirSQL made a rather stirring post recently. He talked about a speaker buddy system to help out new speakers in...
2014-07-25 (first published: 2014-07-21)
7,992 reads
My very first IT job was a bit daunting for me. I really wanted to do my best but I...
2014-07-07
538 reads
Personal Thoughts
Just to be clear, I don't expect everyone to have my same thoughts. I personally fully support SQLServerCentral and...
2014-06-23
479 reads
I've been accepted for SQL Saturday Baton Rouge!
Yes, I am a little excited. I've wanted to become a speaker for...
2014-06-16
511 reads
I think I'd like to do a small short series on documentation. I personally love documentation. I honestly think most...
2014-06-09
732 reads
By Chris Yates
In the rush to adopt artificial intelligence, many organizations have quickly built ethical frameworks,...
By Rohit Garg
What Is TempDB and Why It Matters TempDB is a shared system database in SQL...
By Daniel Janik
Boost Your Azure Fabric Pipelines: Don’t Overlook This Crucial Spark Setting Are your Azure...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Hi all, I have a data flow task with: Flat File Source (csv) ->...
Hi all, I have a data flow task with: Flat File Source (csv) ->...
You're tasked with planning capacity for a new SQL Server database workload. Which of the following is the most accurate way to determine how much CPU, memory, and I/O throughput your workload requires? What single or multiple tools would you use to answer the questions around resource needs?
See possible answers