Skip to main content

Cross Join in SQL-Server


Cross Joins produce results that consist of every combination of rows from two or more tables. That means if table A has n rows and table B has m rows, a CROSS JOIN will result in n X m rows.
There is no Where Condition used in cross join

SQL CROSS JOIN syntax:

SELECT * FROM [TABLE 1] CROSS JOIN [TABLE 2]
OR
SELECT * FROM [TABLE 1], [TABLE 2]


Example

CREATE TABLE [dbo].[Student]
(
[StudID] [int] IDENTITY(1,1) NOT NULL,
[StudName] [varchar](50)
)
CREATE TABLE [dbo].[Division]
(
[DivisionID] [int] IDENTITY(1,1) NOT NULL,
[DivisionName] [varchar](50)
)
INSERT INTO Student(StudName) VALUES('ABC')
INSERT INTO Student(StudName) VALUES('XYZ')
INSERT INTO Division(DivisionName) VALUES('Division 1')
INSERT INTO Division(DivisionName) VALUES('Division 2')
INSERT INTO Division(DivisionName) VALUES('Division 3')


SELECT * FROM Student
CROSS JOIN Division


OUTPUT
We have two table Student and Division corresponding 2 and 3 rows in table cross join return

2 X 3 = 6 Rows

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