Skip to main content

UNION the results of multiple stored procedures with ASP.NET

UNION is used to combine the result from multiple SELECT statements into a single result set.

If we have a stored procedure and need to call several different times passing in different parameters each time. We would like to collect the results as a single dataset.

exec MyStoredProcedure 1
UNION
exec MyStoredProcedure 3
UNION
exec MyStoredProcedure 5

this shows an syntax above but got the error ...

Incorrect syntax near the keyword 'Union'.

You'd have to use a temp table like this.

CREATE TABLE #TempTABLE

{

COLUMN1 datatype

COLUMN2 datatype

}

INSERT #TempTABLE

exec MyStoredProcedure 1

INSERT #TempTABLE

exec MyStoredProcedure 2

INSERT #TempTABLE

exec MyStoredProcedure 3


EXAMPLE

create table users

(

userId int identity(1,1) not null,

userName varchar(50) not null,

userPass varchar(20) not null

)

insert into users(userName, userPass) values('UserName1', 'Password')

insert into users(userName, userPass) values('UserName2', 'Password')

insert into users(userName, userPass) values('UserName3', 'Password')

insert into users(userName, userPass) values('UserName4', 'Password')

insert into users(userName, userPass) values('UserName5', 'Password')

insert into users(userName, userPass) values('UserName6', 'Password')


Create the Store procedure

CREATE PROCEDURE Sp_GetUserInformation

@userId INT

AS

BEGIN

SELECT * FROM users WHERE userid=@userId

END

GO


You want to fetch the record whose userid is 1 3 5 and store it into dataset.



CREATE PROCEDURE Sp_Collectalluser

AS

BEGIN

--Create temporary table

CREATE TABLE #TEMP

(

userId INT,

userName VARCHAR(255),

userPass VARCHAR(255)

)

INSERT INTO #TEMP

exec Sp_GetUserInformation 1

INSERT INTO #TEMP

exec Sp_GetUserInformation 3

INSERT INTO #TEMP

exec Sp_GetUserInformation 5

SELECT * FROM #TEMP

END


OUTPUT

After executing the store procedure

UserId

UserName

Userpass

1

UserName1

Password

3

UserName3

Password

5

UserName5

Password


Comments

Popular posts from this blog

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...

ASP.Net AJAX Interview Questions

What is Ajax? Ajax means " Asynchronous Javascript and XM L". Ajax represents a set of commonly used techniques, like HTML/XHTML, CSS, Document Object Model(DOM), XML/XSLT, Javascript and the XMLHttpRequest object, to create RIA's (Rich Internet Applications). ASP.NET AJAX update only a specified portion of data without refreshing the entire page. The ASP.NET AJAX works with the AJAX Library that uses object-oriented programming (OOP) to develop rich Web applications that communicate with the server using asynchronous postback. What are the different controls of ASP.NET AJAX? ASP.NET AJAX includes the following controls: ScriptManager ScriptManagerProxy UpdatePanel UpdateProgress Timer Describe the technology that makes up AJAX?   AJAX is based on the following web standards: XMLHttpRequest Object JavaScript HTML/DHTML DOM XML CSS What role does the ScriptManager play?   The ScriptManager manages all ASP.Net AJAX resour...

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...