By Design
Just because something works, is it prudent to implement a solution knowing there is a chance this design flaw will be stricken from future revs of SQL Server? It depends.
2017-04-10
77 reads
Just because something works, is it prudent to implement a solution knowing there is a chance this design flaw will be stricken from future revs of SQL Server? It depends.
2017-04-10
77 reads
Microsoft's Customer Experience Improvement Program for SQL Server: once easy to avoid, now hard to ignore, but Rodney Landrum sees an upside.
2017-02-06
1,555 reads
Rodney Landrum gets lost in the fourth dimension, while coding the infinite possible combinations of SQL Server dates and times.
2016-02-01
85 reads
2015-09-14
146 reads
In a guest post, Rodney Landrum ponders the gaps in his DBA experience at the edge of Lake Erie.
2015-03-02
124 reads
Conference travel enhances our minds with more than just SQL. It exposes us to new cultures, people and possibilities.
2015-01-05
120 reads
Rodney Landrum on finding the inspiration you need, somehow and from somewhere, to get yourself out of a tight corner.
2014-09-29
131 reads
2014-04-14
161 reads
When DBAs too often find themselves trading sleep for Megabytes, it's time for a different approach to detection and alerting of disk space problems. So argues Rodney Landrum.
2014-01-20
126 reads
An impromptu hacking session, in response to an inexplicably-changed password, reminds Rodney Landrum of some valuable lessons for every DBA.
2013-08-05
119 reads
By ChrisJenkins
Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...
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...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WA:08218154393 Jl. Paus No.81, RT.1/RW.8, Wil, Kec. Pulo Gadung, Kota Jakarta Timur, Daerah Khusus...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
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