Skip to main content

What is the difference between Where and Having Clause?


We always get confused between WHERE and Having clause and make mistakes. Here in this article, I will try to highlight all the major differences between WHERE and HAVING, and things you should be aware of, when using either WHERE or HAVING.

Here is The Difference

Though the HAVING clause specifies a condition that is Similar to the purpose of a WHERE clause, the two clauses Are not interchangeable. Listed below are some differences to help distinguish between the two:
1. The WHERE clause specifies the criteria which individual records must meet to be selected by a query. It can be used without the GROUP BY clause. The HAVING clause cannot be used without the GROUP BY clause.
2. The WHERE clause selects rows before grouping. The HAVING clause selects rows after grouping.
3. The WHERE clause cannot contain aggregate functions. The HAVING clause can contain aggregate functions.
Use HAVING instead of WHERE when you want to establish a condition that involves a grouping (aggregating) function. (Grouping functions are things like count(), max(), sum(), etc.)

EXAMPLE

CREATE TABLE Student(sid INT identity PRIMARY KEY , City Varchar(255) NOT NULL)
INSERT INTO Student(City)VALUES('AL')
INSERT INTO Student(City)VALUES('AK')
INSERT INTO Student(City)VALUES('GA')
INSERT INTO Student(City)VALUES('CA')
INSERT INTO Student(City)VALUES('CA')
INSERT INTO Student(City)VALUES('GA')
INSERT INTO Student(City)VALUES('AK')
INSERT INTO Student(City)VALUES('LA')
INSERT INTO Student(City)VALUES('CA')

SELECT City, COUNT(*)as cnt
FROM student WHERE City IN ('CA', 'LA','AK')
GROUP BY City ORDER BY City

SELECT City, COUNT(*)as cnt
FROM student
GROUP BY City HAVING City IN ('CA', 'LA')
ORDER BY City

OUTPUT

City Cnt
------------------
AK 2
CA 3
LA 1

City Cnt
-------------------
CA 3
LA 1
Labels:

Comments

Post a Comment

Popular posts from this blog

HTTPHandler and HTTPModule in ASP.NET

If you want to implement pre-processing logic before a request hits the IIS resources. For instance you would like to apply security mechanism, URL rewriting, filter something in the request, etc. ASP.NET has provided two types of interception HttpModule and HttpHandler .   The web server examines the file name extension of the requested file, and determines which ISAPI extension should handle the request. Then the request is passed to the appropriate ISAPI extension.  For Example When an .aspx page is requested it is passed to ASP.Net page handler. Then Application domain is created and after that different ASP.Net objects like Httpcontext, HttpRequest, HttpResponse. HTTPModule: -    It's just like a filter. The Modules are called before and after the handler executes . -    HTTP Modules are objects which also participate the pipeline but they work before and after the HTTP Handler does its job, and produce additional serv...
124 comments
Read more

Connected and disconnected architecture in ADO.Net with Example

Connected Architecture of ADO.NET The architecture of ADO.net, in which connection must be opened to access the data retrieved from database is called as connected architecture. Connected architecture was built on the classes connection, command, datareader and transaction.  Connected architecture is when you constantly make trips to the database for any CRUD (Create, Read, Update and Delete) operation you wish to do. This creates more traffic to the database but is normally much faster as you should be doing smaller transactions. Disconnected Architecture in ADO.NET The architecture of ADO.net in which data retrieved from database can be accessed even when connection to database was closed is called as disconnected architecture. Disconnected architecture of ADO.net was built on classes connection, dataadapter, commandbuilder and dataset and dataview. Disconnected architecture is a method of retrieving a r...
39 comments
Read more

What is AutoEventWireup?

The ASP.NET page framework also supports an automatic way to associate page events and methods. If the AutoEventWireup attribute of the Page directive is set to true (or if it is missing, since by default it is true ),  AutoEventWireup is an attribute in Page directive.   AutoEventWireup is a Boolean attribute that indicates whether the ASP.NET pages events are auto-wired.  AutoEventWireup will have a value true or false . By default it is true . <% @ Page Language ="C#" AutoEventWireup ="true" CodeBehind ="Default.aspx.cs" Inherits ="WebApplication2._Default" %> the page framework calls page events automatically, specifically the Page_Init and Page_Load methods. In that case, no explicit Handles clause or delegate is needed. Example 1 With AutoEventWireup ="true" HTML Code <% @ Page Language ="C#" AutoEventWireup ="true" CodeBehind =...
1 comment
Read more