Skip to main content

FOR XML

In a FOR XML clause, you specify one of these modes:

RAW - generates a single <row> element per row in the rowset that is returned by the SELECT statement
AUTO - generates nesting in the resulting XML by using heuristics based on the way the SELECT statement is specified
EXPLICIT - provides the most flexibility in generating the XML
PATH - a simpler alternative to writing EXPLICIT mode queries

Examples for RAW:  

Query 1:  Basic
                      SELECT doc_id ,
                                     media_id
                      FROM DOC
                      FOR XML RAW
Result 1:
                      <row doc_id="114" media_id="-117" />
                      <row doc_id="115" media_id="-113" />

Query 2:  Using Customized name instead of "row" in the result
                      SELECT doc_id ,
                                     media_id
                      FROM DOC
                      FOR XML RAW('DOC')
Result 2:
                      <DOC doc_id="114" media_id="-117" />
                      <DOC doc_id="115" media_id="-113" />



Examples for AUTO:

Query 1:  Basic
                      SELECT doc_id ,
                                     media_id
                      FROM DOC
                      FOR XML AUTO
Result 1:
                      <DOC doc_id="114" media_id="-117" />
                      <DOC doc_id="115" media_id="-113" />

Note : If we specifies a four-part name in the query, the server name is not returned in the resulting XML document when the query is executed on the local computer. However, the server name is returned as the four-part name when the query is executed on a network server.

Query 2: Four Part Name
                      SELECT doc_id ,
                                     media_id
                      FROM Server.Database.Owner.Table
                      FOR XML AUTO
Result 2:
                      <Server.Database.Owner.Table doc_id="114" media_id="-117" />
                      <Server.Database.Owner.Table doc_id="115" media_id="-113" />

Query 3: Using Alias
                      SELECT doc_id ,
                                     media_id
                      FROM Server.Database.Owner.Table DOC
                      FOR XML AUTO
Result 3:
                      <DOC doc_id="114" media_id="-117" />
                      <DOC doc_id="115" media_id="-113" />

Examples for EXPLICIT:

Query 1:  Basic
                      SELECT TOP 1                      
                              1 AS Tag ,                                        --- statements to be used as is
                              NULL AS Parent ,                            --- statements to be used as is
                              E.Doc_Id AS [Layer1!1!Emp] ,                             --- outer column
                              E.Custodian_Id AS [Layer2!2!Layer3!ELEMENT]  --- inner column
                      FROM    dbo.Doc AS E
                      UNION ALL
                      SELECT TOP 1
                              2 AS Tag ,                                          --- statements to be used as is
                              1 AS Parent ,                                      --- statements to be used as is
                              E.Doc_Id ,                                                            --- outer column
                              E.Custodian_Id                                                        --- inner column
                      FROM    dbo.Doc AS E
                      ORDER BY [Layer1!1!Emp] ,[Layer2!2!Layer3!ELEMENT] -- order by is very important to get a nested loop
                      FOR     XML EXPLICIT ;

Result 1: 
                      <Layer1 Emp="1569">
                        <Layer2>
                          <Layer3>0</Layer3>
                        </Layer2>
                      </Layer1>

Examples for PATH:

Query 1:  Basic
                       SELECT  doc_id ,
                              media_id
                      FROM    dbo.Doc
                      FOR     XML PATH('')     
 Result 1: 
                      <doc_id>11491190</doc_id>
                      <media_id>-11737</media_id>

Query 2:  Using Alias
                      SELECT  doc_id ,
                              media_id
                      FROM    dbo.Doc
                      FOR     XML PATH('CustomerInfo') ;
Result 2: 
                      <CustomerInfo>
                        <doc_id>11491190</edoc_id>
                        <media_id>-11737</media_id>
                      </CustomerInfo>

Labels:

Comments

Post a Comment

Popular posts from this blog

Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)

While accessing the active directory (AD) and authorization manager (AZMAN) , If you get “   Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)  “ message check the    account that is being used to get the LDAP query from AD .  ERROR DETAILS Exception Details:  System.Runtime.InteropServices.COMException: Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098) Source Error: Line 154:    'Session("FullName") = System.Security.Principal.WindowsIdentity.GetCurrent.Name.ToString() Line 155: Line 156:    If Not User.IsInRole("Role1") Then Line 157:          Response.Redirect("./Login.aspx") Line 158:    End If  Stack Trace : .... SOLVE IT Steps to do check the app pool rights: Click on the website name that you are having problem with in IIS  In the right panel you will see 'Basic Settings'. Click It. Select the specific pool option and enter the name of the ac
Post a Comment
Read more

Sql Server database Read_Only / Read_Write

The ALTER DATABASE command allows a database administrator to modify SQL Server databases and their files and filegroups. This includes permitting the changing of database configuration options. Why Read Only ? When you need to ensure that the data is a database is not modified by any users or automated processes, it is useful to set the database into a read-only mode. Once read-only, the data can be read normally but any attempts to create, updated or delete table rows is disallowed. This makes the read-only mode ideal when preparing for data migration, performing data integrity checking or when the data is only required for historical reporting purposes. Make Database Read Only USE  [master] GO ALTER DATABASE  [TESTDB]  SET  READ_ONLY  WITH  NO_WAIT GO Make Database Read/Write USE  [master] GO ALTER DATABASE  [TESTDB]  SET  READ_WRITE  WITH  NO_WAIT GO In case you get the following error message make the database single user: Msg 5070, Level 16, Stat
Post a Comment
Read more

Do's and Don't SQL

Do's: Writing comments whenever something is not very obvious, as it won’t impact the performance.  (--) for single line  (/*…*/) to mark a section Use proper indentation Use Upper Case for all SQL keywords. SELECT, UPDATE, INSERT, WHERE, INNER JOIN, AND, OR, LIKE. Use BEGIN... END block for multiple statements in conditional code  Use Declare and Set in beginning of Stored procedure Create objects in same database where its relevant table exists otherwise it will reduce network performance. Use PRIMARY key in WHERE condition of UPDATE or DELETE statements as this will avoid error possibilities. If User table references Employee table than the column name used in reference should be UserID where User is table name and ID primary column of User table and UserID is reference column of Employee table. Use select column name instead of select * Use CTE (Common Table Expression); its scope is limited to the next statement in SQL query, instead of temporary tables and der
Post a Comment
Read more