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
100 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
100 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,601 reads
Rodney Landrum gets lost in the fourth dimension, while coding the infinite possible combinations of SQL Server dates and times.
2016-02-01
125 reads
2015-09-14
184 reads
In a guest post, Rodney Landrum ponders the gaps in his DBA experience at the edge of Lake Erie.
2015-03-02
168 reads
Conference travel enhances our minds with more than just SQL. It exposes us to new cultures, people and possibilities.
2015-01-05
164 reads
Rodney Landrum on finding the inspiration you need, somehow and from somewhere, to get yourself out of a tight corner.
2014-09-29
173 reads
2014-04-14
185 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
141 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
139 reads
By SQLPals
How to Clear the SSMS Cache (SSMS 21 and Later) Updated...
By Arun Sirpal
“What exactly did it do on my server?” is the first question a DBA...
By James Serra
Microsoft shared a broad set of Fabric, Power BI, and SQL updates at FabCon...
Comments posted to this topic are about the item Let's Talk Certifications
Comments posted to this topic are about the item The Hidden Security Risks of...
Comments posted to this topic are about the item The Empty Aggregate
I have this table in a SQL Server 2025 database:
CREATE TABLE [dbo].[CustomerOrder] ( [OrderID] [int] NULL, [CustomerID] [int] NULL, [total] [money] NULL ) ON [PRIMARY] GOWhat is returned from this code? (answers are for the sum and then the count)
SELECT SUM(total) AS sum,
COUNT(total) AS count
FROM dbo.CustomerOrder;
See possible answers