T-SQL Tuesday #100: Looking Forward
The future, 100 months from now: It’s Monday, 6 July 2026. It’s been quite a week since SQL Server Update...
2018-03-13
302 reads
The future, 100 months from now: It’s Monday, 6 July 2026. It’s been quite a week since SQL Server Update...
2018-03-13
302 reads
This post continues our look at date and time data types in SQL Server. SQL Server 2008 introduced new data...
2018-03-07
417 reads
Last week I spoke about a world wary data type for storing dates and times in a single column, with...
2018-02-28
1,074 reads
Last year I ran a series of posts about Database Fundamentals. Over the next few weeks, I will cover the...
2018-02-21
343 reads
Nested views are bad. Let’s get that out of the way. What is a nested view anyway? Imagine that you...
2018-02-14
2,387 reads
Tom Roush The SQL Family lost a much admired member to cancer last month, Tom Roush. In our little community,...
2018-02-07
400 reads
Victoria is on an island off the coast of Vancouver, British Columbia. The island is wisely called Vancouver Island. It...
2018-01-31
529 reads
As I mentioned a couple of weeks ago, I will be presenting for the first time at SQLBits in London,...
2018-01-24
336 reads
By now you have probably seen the news about a major flaw in the design of CPUs from all major...
2018-01-17
340 reads
A year ago, I wrote in a post that cloud computing is just someone else’s data center. I was wrong. Whether...
2018-01-10
374 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