Export (0) Print
Expand All
1 out of 1 rated this helpful - Rate this topic

About This Release

SQL Server 2000

Microsoft® SQLXML 3.0 Service Pack 3 includes bug fixes and the following enhancements:

  • XML bulk load ID propagation

    When bulk loading XML in tables related by primary key/ foreign key relationships, and the primary key column is an identity type column for which SQL Server generates the values, these values are appropriately propagated in the foreign key columns. For a working sample see, Examples of Bulk Loading XML Documents.

  • NULL handling in SOAP messages

    In sending a SOAP request from Visual Studio .NET 2003, you can pass a NULL for value-typed parameters (integers, booleans, ...). For more information see, Guidelines and Limitations of SOAP Support in SQLXML.

The documentation for this service pack includes information about the following:

  • IIS Virtual Directory Management for SQL Server

    This utility was introduced in SQL Server 2000 and further enhanced in SQLXML. This documentation contains the complete and updated version of the "IIS Virtual Directory Management for SQL Server" section in SQL Server Books Online for SQL Server 2000. For more information, see IIS Virtual Directory Management for SQL Server.

  • Client-side FOR XML

    The FOR XML clause, first introduced in SQL Server 2000, allows you to request query results to be returned as XML. The formatting is done on the server. SQLXML 3.0 enhanced this functionality by introducing client-side XML formatting. For more information see, Retrieving XML Documents by Using FOR XML on the Client Side

  • Web services (SOAP) support

    Web services support in Microsoft SQLXML exposes Microsoft SQL Server™ 2000 as a Web service that offers SQL Server functionality to the client. You can send SOAP HTTP requests to the server that is running SQLXML to execute stored procedures, user-defined functions (UDFs), and templates. For more information, see Web Services (SOAP) Support in SQLXML.

  • XML views using annotated XSD schemas

    You can create XML views of relational data by using annotated XML Schema Definition language (XSD) schemas. The annotated XML-Data Reduced language (XDR) schemas (introduced in Microsoft SQL Server 2000) are also supported. For more information, see Creating XML Views by Using Annotated XSD Schemas.

  • Updategram

    You can modify (insert, update, or delete) rows in a database in Microsoft® SQL Server™ 2000 from an existing XML document by using an updategram. Updategrams work with XML views. For more information, see Using Updategrams to Modify Data.

  • XML Bulk Load

    XML Bulk Load is a stand-alone COM object that allows you to load XML data into Microsoft® SQL Server® tables. For more information, see Performing Bulk Load of XML Data.

  • Data access components

    The following data access components are supported:

    • SQLXMLOLEDB Provider

      The SQLXMLOLEDB Provider exposes Microsoft® SQLXML functionality through ADO. For more information, see SQLXMLOLEDB Provider.

    • SQLXML Managed Classes

      This object model exposes the functionality of SQLXML within the Microsoft .NET Framework. With this provider, you can write a C# application to access XML data from an instance of SQL Server, bring the data into the .NET environment, process the data, and then send the data back in a XML document (the DiffGram) to apply the updates to SQL Server. For more information, see SQLXML Managed Classes.

  • DiffGrams

    The DiffGram format is introduced in the DataSet component of the Microsoft .NET Framework. Within the .NET Framework, you can create DiffGrams and then use them to modify data in tables in a SQL Server 2000 database. This release introduces the parentId annotation. This annotation establishes parent-child relationships among elements in the DiffGram. SQLXML uses this information when it applies updates. For more information, see Using DiffGrams to Modify Data.

  • Other enhancements
    • Since the release of SQL Server 2000, enhancements have been made to the syntax for accessing database objects by using HTTP, XML templates, annotated XDR schemas, and XPath queries. For more information about these enhancements, see Other Feature Enhancements.

    • The XML Bulk Load samples are updated to use XSD schemas. The samples continue to show equivalent XDR schemas.

    • The updategram samples are updated to use XSD schemas. The samples continue to show equivalent XDR schemas.

    • The XSL namespace "http://www.w3.org/TR/WD-xsl" is no longer supported. The XSLT namespace "http://www.w3.org/1999/XSL/Transform" version 1.0 continues to be supported.

    SQLXML 3.0 is not completely backward compatible with SQLXML 2.0 and SQLXML Web Release 1 because of some bug fixes and minor functional changes. Although most applications will run without modification, you must test them before putting them into production with SQLXML 3.0.

Understanding the Side-by-Side Installation Issues

The installation process for SQLXML 3.0 does not remove the files that were installed by Web Release 1 or SQLXML 2.0. Therefore, you can have the DLLs for all three installations on your computer. You can run the installations side-by-side. SQLXML 3.0 includes version-independent and version-dependent PROGIDs. All production applications should use version-dependent PROGIDs.

SQL Server Virtual Directory Management Issues
  • Configure IIS Support is added to the SQLXML 3.0 program group. Use this shortcut to create virtual directories to use SQLXML 3.0 functionality.

  • If you have previously created Microsoft Visual Basic® applications and you want to use SQLXML 3.0, you must recompile the application with reference to Sqlvdr3.dll.

  • For Microsoft Visual Basic Scripting Edition (VBScript) applications, you must register the DLL that you want to use. In the following example, if you specify version-independent PROGIDs, the application depends on the last registered DLL:
    set objControl = CreateObject("SQLVDir.SQLVDirControl") 
    

    The version-dependent PROGID is SQLVDir.SQLVDirControl.3.0.

  • In the Microsoft Management Console (MMC) snap-in for the SQL Server Virtual Directory Management utility, in the Properties dialog box of the previously created virtual directories, there is an additional tab called Version 3. This tab allows you to upgrade those virtual directories to SQLXML 3.0. After you upgrade the virtual directories, this tab disappears from the dialog box. The upgraded virtual directories can be used for SQLXML SOAP functionality.

  • When you create a virtual directory by using SQLXML 3.0, the ISAPI location (Advanced tab on the Properties dialog box) points by default to Sqlis3.dll.
Bulk Load Issues
  • If you have previously created Visual Basic applications and you want to use SQLXML 3.0, you must recompile the application with reference to Xblkld3.dll.

  • For Visual Basic Scripting Edition applications, you must register the DLL you want to use. In the following example, if you specify version-independent PROGIDs, the application depends on the last registered DLL:
    set objBulkLoad = CreateObject("SQLXMLBulkLoad.SQLXMLBulkLoad") 
    

    The version-dependent PROGID is SQLXMLBulkLoad.SQLXMLBulkLoad.3.0.

Registry Key Changes

In SQLXML 3.0, the registry keys have changed from the earlier releases to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SQLXML3\TemplateCacheSize

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SQLXML3\SchemaCacheSize

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SQLIS3\NumThreads

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SQLIS3\MaxRequestQueueSize

You must change the settings if you want these keys to be in effect for SQLXML 3.0.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.