INTRODUCTION Client-Side XML-Based APIs and SQL Server 2005

INTRODUCTION Client-Side XML-Based APIs and SQL Server 2005 Integration XML is ubiquitous in the SQL Server 2005-era client APIs. User-defined types use .NET XML Serialization to be able to be marshaled or persisted as XML directly. The FOR XML syntax has been extended to allow a user to fetch data in an XML type. In addition, SQL Server Analysis Services can directly consume queries in XML format and produce XML results. This is called XML for Analysis and has been around for a while; in SQL Server 2005 it becomes a first-class API directly supported and on a par with OLE DB for Analysis. If you ve gotten used to OLE DB for Analysis (or its automation equivalent, ADOMD), don t fret XML for Analysis uses an OLE DB style syntax, for both queries and properties. The XML data type and the XQuery engine inside SQL Server 2005 are complemented by a rich middle-tier or client-side model for XML. This model exposes XML data outside the server using a variety of data models. These models include the XML Document Object Model (DOM) and abstract XmlNavigator model, in addition to streaming models known as XmlReader and XmlWriter. The standard XML query and transformation models, XPath and XSLT, have been part of the .NET platform since its inception and are being extended to support client-side XQuery and XPath 2.0. The XmlReader and XmlWriter classes are being enhanced to enable support of the XQuery 1.0 and XPath 2.0 XML data model. This is necessary because the new XML data model differs from the XML 1.0 and name- spaces model. The XQuery 1.0 and XPath 2.0 data model extends the weakly typed nodeset model to include strongly typed sequences consisting of nodes, atomic values, or a combination of both. In addition, this data model is a closed data model, meaning that running an XQuery against an instance of the data model is guaranteed to produce an instance of the data model. In addition, enhancements to the XPathDocument class will enable it to support in-place editing and change tracking, and marshaling of sets of changes. This makes the in-memory client-side XML model on a par with the client-side relational DataSetclass. In a revolutionary approach to querying XML data from the client, a generalized client-side parsing and execution engine, known as the common query abstraction, will allow XPath, XSLT, and XQuery syntax to be compiled into an intermediate query format, in a method analogous to high-level languages being compiled into IL code. This allows programmers to use the query language that is most suitable for the job or the one that they are most familiar with. The query abstraction is extensible so that

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Adult Web Hosting services

Bookmark the permalink.

Comments are closed.