I have been working with SQL Server for quite a few years now, and it still happens quite often that I discover new cool things to do in t-sql. My latest discovery is not a new feature at all, because it was introduced back in SQL Server 2005 – but for some reason I haven’t come across it before. So I thought I might share it with you
Consider the following example:
CREATE TABLE AggregatedClientRequests ( Id INT IDENTITY PRIMARY KEY, ClientIp VARCHAR(200) NOT NULL, NumOfRequests INT NOT NULL ) GO INSERT INTO AggregatedClientRequests (ClientIp, NumOfRequests) VALUES ('18.104.22.168', 5100), ('22.214.171.124', 10000), ('126.96.36.199', 200), ('188.8.131.52', 44000), ('184.108.40.206', 2200), ('220.127.116.11', 10000), ('18.104.22.168', 31000), ('22.214.171.124', 100), ('126.96.36.199', 300), ('188.8.131.52', 10000) GO
This table holds an aggegated value of the number of requests a given ClientIp has made on a system. Now you want to identify the top three ClientIps that have generated the most requests. That easy, right? Without thinking too much about it, I would have written something like this:
SELECT TOP (3) * FROM AggregatedClientRequests ORDER BY NumOfRequests DESC
That looks right… or does it? What about the ClientIps ‘184.108.40.206’ and ‘220.127.116.11’ ? They also generated 10.000 requests, so they are actually equally to the ‘18.104.22.168’ ip. So which one of the three with 10.000 request should I return?. If I want those returned as well (think of a use case where the top three are sales persons that should have a bonus), how could I do that? That’s actually pretty simple by using the TOP WITH TIES clause like this:
SELECT TOP (3) WITH TIES * FROM AggregatedClientRequests ORDER BY NumOfRequests DESC
Now it get this back:
Notice that I actually get 5 rows returned, even though my TOP clause stated that I only wanted three! The WITH TIES clause looks at the last row of the TOP (3) rows, and add all other rows with identical values.
How simple is that?! I don’t even want to think about how the query would look to achieve the same thing without using the WITH TIES clause. Perhaps you will give it a go?