Skip to main content

SQL SERVER : Selecting data from temporary tables & table variables using FOR XML

We can
convert the relational data stored in the table into XML by using the FOR XML
syntax, I am not going to the explain all the features of FOR XML.



Physical table


SELECT * FROM ASPNET_Roles FOR XML AUTO,ROOT ('A'),ELEMENTS

this select statement will give the following output

<A><URR_ASPNET_Roles>
<ApplicationId>AFFE3DDD-ABAD-49DF-A144-DA87BE69B90E</ApplicationId>
<RoleId>89C306A6-2D21-42AB-A42F-5029091CB4E8</RoleId>
<RoleName>SBU
User</RoleName>
<LoweredRoleName>sbu
user</LoweredRoleName>
<USER_TYPE>2</USER_TYPE>
</URR_ASPNET_Roles>
<URR_ASPNET_Roles>
<ApplicationId>AFFE3DDD-ABAD-49DF-A144-DA87BE69B90E</ApplicationId>
<RoleId>180BA05D-D2A5-49CA-BED3-3C6F080F6543</RoleId>
<RoleName>Super
User</RoleName>
<LoweredRoleName>super
user</LoweredRoleName>
<USER_TYPE>1</USER_TYPE>
</URR_ASPNET_Roles>
</A>


its is a perfect xml with all the nodes and 'A' as the root element

now consider selecting the data from temporary table & table variable


SELECT *
INTO #TBL_TMP FROM
ASPNET_Roles

the values of the table URR_ASPNET_Roles is inserted into temporary table #TBL_TMP

SELECT *
FROM #TBL_TMP FOR
XML AUTO,ROOT('A'),ELEMENTS

the above select statement will produce the following output

<A>
<_x0023_TBL_TMP>
<ApplicationId>AFFE3DDD-ABAD-49DF-A144-DA87BE69B90E</ApplicationId>
<RoleId>89C306A6-2D21-42AB-A42F-5029091CB4E8</RoleId>
<RoleName>SBU
User</RoleName>
<LoweredRoleName>sbu
user</LoweredRoleName>
<USER_TYPE>2</USER_TYPE>
</_x0023_TBL_TMP>
<_x0023_TBL_TMP>
<ApplicationId>AFFE3DDD-ABAD-49DF-A144-DA87BE69B90E</ApplicationId>
<RoleId>180BA05D-D2A5-49CA-BED3-3C6F080F6543</RoleId>
<RoleName>Super
User</RoleName>
<LoweredRoleName>super
user</LoweredRoleName>
<USER_TYPE>1</USER_TYPE>
</_x0023_TBL_TMP>
</A>


but what is _x0023_
doing in output, from where did it originate ? how can we remove this
addition in the xml tag

consider the following statement

SELECT *
FROM #TBL_TMP TBL_TMP
FOR
XML AUTO,ROOT('A'),ELEMENTS

this will produce the following output

<A>
<TBL_TMP>
<ApplicationId>AFFE3DDD-ABAD-49DF-A144-DA87BE69B90E</ApplicationId>
<RoleId>89C306A6-2D21-42AB-A42F-5029091CB4E8</RoleId>
<RoleName>SBU
User</RoleName>
<LoweredRoleName>sbu
user</LoweredRoleName>
<USER_TYPE>2</USER_TYPE>
</TBL_TMP>
<TBL_TMP>
<ApplicationId>AFFE3DDD-ABAD-49DF-A144-DA87BE69B90E</ApplicationId>
<RoleId>180BA05D-D2A5-49CA-BED3-3C6F080F6543</RoleId>
<RoleName>Super
User</RoleName>
<LoweredRoleName>super
user</LoweredRoleName>
<USER_TYPE>1</USER_TYPE>
</TBL_TMP>
</A>

the output is clean with no extra additions !!!

How ? in the second statement we have provided an alias for the table which is
displayed in the output

same is the case with table variable's

DECLARE @tblVar TABLE
(ID INT,DATA
VARCHAR(10))

INSERT INTO @tblVar
VALUES (1,'DATA1')

SELECT *
FROM @tblVar FOR
XML AUTO,ROOT('A'),ELEMENTS

<A>
<
_x0040_tblVar>
<ID>1</ID>
<DATA>DATA1</DATA>
</
_x0040_tblVar>
</A>

SELECT *
FROM @tblVar TBLVAR FOR
XML AUTO,ROOT('A'),ELEMENTS

<A>
<TBLVAR>
<ID>1</ID>
<DATA>DATA1</DATA>
</TBLVAR>
</A>


why are such additional unwanted strings displayed in temporary tables and table
variables and not in the case of physical tables

temporary tables and table variables have # & @ attached to their names
respectively, so these special characters are parsed by SQL server and converted
into xml, in both cases we can remove these unwanted additions by using aliases.


Happy programming

Comments

Popular posts from this blog

SCRUM- Who should write a user story

Traditionally user stories (or requirements) were written by Business analysts. They used to prepare big documents after months of study. It was a herculean task. I used to get such UI/Functional specification documents. I have fixed a lot of bugs because I missed few text in such 1000 + pages document. This is not the only interesting part. Some of the requirements were so weird that I often wondered why I am creating the features which no one is going to use. If I had the option I would have recommended a better option. If the BA’s misunderstood some requirements & customers failed to correct those few words in the epic requirement then we will have a nice situation. In the agile world the story is different. Product Owners are primarily responsible for user stories. But can anyone else also contribute? Yes. Definitely yes In actual environment many users write user stories. The first requirement may come from end user. The PO, tech architect, scrum master, BA’s... anyone can up

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices. Some of the rules  The roles of Scrum • Scrum Master -  http://www.theagileschool.com/2012/03/scrummasters-checklist-roles.html • Product Owner • Feature Team The PDCA cycle ( http://www.theagileschool.com/2012/05/pdca-scrum-or-agile-why-is-it-important.html  )  frequent communication about risks (daily) • Plan – Sprint planning • Do – Actual engineering sprint – deliver a potential shippable code • Check – Sprint review • Act – Retrospective  The scrum guide @ http://www.scrum.org/Scrum-Guides will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum. Apart from these rest of

Product Backlog: Should you write everything in user story format?

I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes.   I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. Once I