2015-12-21
327 reads
2015-12-21
327 reads
Louis Davidson explains why a little database courtesy goes a long way.
2015-11-16
232 reads
Whose fault is it if a database is hacked and its contents appear on a hacker’s site? Louis Davidson suggests that, regardless of limitations, the DBA always bears some responsibility.
2014-12-22
163 reads
2014-11-24
169 reads
In opera, tragedy or absurdity happens because the characters are incapable of standing back, and making a difficult decision. Instead, at every stage, they just drift towards their fate by taking the easy option. Don't let the same fate befall you, as a DBA.
2014-08-04
120 reads
Louis Davidson on why DBAs ought to do one thing, every day, that is scary.
2014-07-07
238 reads
As a professional, our knowledge of a given task should extend, at a minimum, one level deeper than is strictly necessary to perform the task. Anything deeper can be left to the ridiculously smart, or obsessive, or both
2014-05-12
126 reads
Louis Davidson on the small dreams that DBAs can nurture, each day, to elevate the drudgery of a seemingly banal task into a celebration of purpose.
2014-03-03
177 reads
Like Sherlock Holmes, a DBA needs the sound deductive reasoning to pinpoint the root cause of a crime, in amongst a thousand interesting but irrelevant details.
2013-11-18
142 reads
Technical debt is frustrating but dealing with it requires patience. Louis Davidson explains why.
2013-09-02
143 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