SQL Server 2000 and XML: Developing XML-Enabled Data Solutions for the Web

Review

Nine Reasons For Using XML

1. Division of Labor. Different team members have different skills, and a well-architected solution maximizes each team member's skill set. To do this effectively, you must abstract the relational data model from the front-end developers.
   
2. One transaction, one place. XML provides entire transactions and complex datasets in a single, portable entity. This portable data container is a leap forward over recordsets or other proprietary data formats.
   
3. Look to the future. Microsoft has adopted XML as one of the key technologies for the .NET platform, which we will discuss as we examine .NET Enterprise Servers.
   

XML and XSLT

XML with SQL Server 2000

SQL Query Extensions

SQL Templates

<persons xmlns:sql="urn:schemas=microsoft=com:xml=sql">
    <sql:xpath-query mapping-schema=:.\persons.xsd:>
        person
    </sql:xpath-query>
</persons>

SQL Updategrams

The Sample Applications

Solution 1

Solution 2

Solution 3

Solution 4

private void Page_Load(object sender, System.EventArgs e)
{
    // Put user code to initialize the page here
    XmlDocument doc = new XmlDocument();
    doc.Load("http://localhost/pubs/templates/alldata.xml");
    ctlXML.Document = doc;
    ctlXML.TransformSource = "xsl\\authors3.xsl";
}

Solution 5

1. To start, we created a new dataset class using the XSD schema that we saw earlier by right-clicking Project | Add Component | Data Set. This creates a new XSD file and an underlying CS file that is autogenerated by Visual Studio. Then we pasted our schema (which we created by hand) into the XSD file. Alternatively, you could use the XML designer to create the XSD file.
   
2. Next, we dragged a DataSet component from the Toolbox onto the page. This opened a wizard where we created a typed dataset based on the dataset class created in Step 1. We called the dataset dsPersons and updated the Page_Load event handler to retrieve the data from SQL Server 2000 using HTTP, as you can see in the code in Figure 22.
   
3. From there, we dragged a DataGrid component from the Toolbox onto the ASPX page by right-clicking Datagrid | Property Builder. We selected dsPersons as the DataSource and person as the data member.
   
4. Next we used the Property Builder to select the columns we wanted to display.
   
5. From there, we configured the Paging, Format, and Borders areas in the Property Builder. We added an event handler for the OnPageIndexChange event (by adding the attribute OnPageIndexChanged="dgperson_PageIndexChanged" to the <asp:DataGrid> tag in the .aspx file. The following code from dotnetgrid.aspx.cs shows the server-side implementation to change the pages.
   

   public void dgperson_PageIndexChanged(object source, 
     System.Web.UI.WebControls.DataGridPageChangedEventArgs e)
   {
     dgperson.CurrentPageIndex = e.NewPageIndex;
     dgperson.DataBind();
   }
   

Performance

Conclusion