Skip to main content

Common Table Expressions in SQL Server - CTE

A common table expression (CTE) can be thought of as a temporary result set that is defined within the execution scope of a single SELECT, INSERT, UPDATE, DELETE, or CREATE VIEW statement. A CTE is similar to a derived table in that it is not stored as an object and lasts only for the duration of the query. Unlike a derived table, a CTE can be self-referencing and can be referenced multiple times in the same query.


In simple layman's terms, CTE basically provides data at the runtime which may come from multiple tables. For e.g. if we have different tables like emp, dept, salgrade etc. then CTE can help in getting the resultset/dataset from multiple tables and form a temporary table. Then we can refer this table within other query any number of times. 


For e.g. if we want to display the following:


Deptno
Dname
Location
TotalCount
10
Hotel Management
Amritsar
6
20
Information Technology
Chicago
1
30
Finance
Ludhiana
2

Now in the above example there are two tables used i.e. 
a. Emp - which stores the information about the employees with their deptno.
b. Dept - which acts as the master of the Department information


The 'total count' column is generated from the 'Emp' table with the help of CTE and then referred in the other query to display dept wise information. The following is the syntax of the CTE that is used to generate the result as mentioned above.



With TotalNoOfEmployeesDeptWise(Deptno, TotalCount) as 
(
Select Deptno, COUNT(*) from Emp group by Deptno
)
Select Dept.Deptno, Dept.Dname, Dept.Location, x.TotalCount from Dept, TotalNoOfEmployeesDeptWise x
where X.Deptno=Dept.Deptno

So as you can see in the code, the first line, starting with 'With', the CTE starts and generates a runtime dataset.
And 'Select' is actual query that is referring to the CTE for displaying information.






Comments

Gagan Jagdev said…
Really a good article, thanks for sharing

Popular posts from this blog

SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

If we encounter this error "SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)" in SQL Server in which the job fails because of the user account related problem, then we need to take the following steps to make it work: a. Go to SQL Server Agent. b. Then select the job which is giving error and not running successfully. c. Then choose properties and in the General Tab, change the owner to "SA" or any account that has the administrative privileges. The problem will be resolved.

Connecting Nodejs to SQL Server with Knex ORM - Part 1

Normally we connect Nodejs to the databases like SQLite, MongoDB, Postgres etc . In this multiple part post, I am going to show you, how we can connect Nodejs with Microsoft's SQL Server using Knex and run CRUD operations. 1. Installation of required packages In order to connect Nodejs to SQL Server with Knex, we will need following node packages installation: i. npm install knex ii. npm install mssql Once the packages are installed, we can write the following code to connect: //Code to KNEX connection settings. var knex = require('knex')({ client: 'mssql', connection: { user: 'sa', password: 'pwd', server: 'localhost', database: 'Test' } }); //Code to query the Table DEPT knex.select("*").from("dept") .then(function (depts){ depts.forEach((dept)=>{ //use of Arrow Function console.log({...dept}); }); }).catch(function(err) { ...

How to use QueryExtenderControl in ASP.NET with LINQ

Queryextender control is a control that helps in doing actions like filtration, searching, sorting etc. on the LINQ Data source with few steps. In fact we don’t have to write any code with this. Screenshot given below is just an example that can easily be achieved through this control. In the above screenshot, we can see that there is a GridView Control that has been binded to a LINQData Source Control. And we have a DropDownlistBox that is also binded to another LINQData Source Control and displaying only grouped jobs. The GridView display all the employees who are matching the Job Parameter. This is done through QueryExtender Control. Also we can search for any name in the employee name's through Query Extender control. The code in the HTML goes like: < form id ="form1" runat ="server">     < div >         Select Job: < asp : DropDownList ID ="Job" runat ="server" DataSourceID ="LinqDataSource2...