Sometimes, you have to fix it yourself
The Problem
SQL Server is a huge product with lots of moving parts. Bugs happen. Microsoft has a place to voice...
2010-02-24
2,200 reads
The Problem
SQL Server is a huge product with lots of moving parts. Bugs happen. Microsoft has a place to voice...
2010-02-24
2,200 reads
The over-reliance on a familiar tool is best described with the quote, “if all you have is hammer, everything looks...
2010-02-23
4,134 reads
Many companies have a very rigid development lifecycle for all products or solutions they develop. Deploying to each of these...
2010-02-23
3,142 reads
In a previous post I showed you how to access variables from within an SSIS script component. More specifically I...
2010-02-22
3,693 reads
Through a circuitous route, I encountered a meaningful, thought-provoking quote lately: "... the best way to predict the future is to...
2010-02-19
1,676 reads
Over and over again we are told that the DMV’s only hold data since your last reboot. So, how do...
2010-02-19
2,937 reads
I have been pondering recently what helps me to sleep at night. Or, conversely, what prevents me from sleeping at...
2010-02-18
1,609 reads
A relatively common requirement in ETL processing is to break records into disparate outputs based on an alphabetical split on...
2010-02-12
1,423 reads
In Part I and Part II of the series, I discussed documenting and discovering Primary Keys and Clustered Indexes. In...
2010-02-11
974 reads
In our world sometimes it’s worth the time and effort for in depth tuning to get the machine to run...
2010-02-10
794 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers