Export (0) Print
Expand All

Guidelines and Limitations

SQL Server 2000
  • To display the Microsoft® SQLXML 3.0 error messages in Microsoft Internet Explorer, on the Tools menu, click Internet Options; and then on the Advanced tab, clear Show friendly HTTP error messages.

  • The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SQLIS3\NumThreads, if present, defines the number of threads that are spawned by the ISAPI to handle HTTP requests. If this registry key is not present in the registry, the default value is (2 * the number of processors) + 1. The minimum value is 1, and the maximum value is 256.

  • The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SQLIS3\MaxRequestQueueSize, if present, defines the queue size for storing HTTP requests waiting to be scheduled. If this registry key is not present in the registry, the default value is 3000 bytes. The minimum value is 1 byte, and the maximum value is 10000 bytes.

  • XML returned as a query result is not validated against the mapping schema that generated the XML.

  • SQLXML 3.0 includes version-independent and version-dependent PROGIDs. It is recommended that all production applications use version-dependent PROGIDs. This is especially important because SQLXML 3.0 is not fully backward compatible. Using version dependent PROGIDs protects from possible production failures when you  install newer releases. From release to release, program behavior may change due to several reasons, such as bug fixes, possible design changes, and so on. Using version-dependent PROGIDs protects from unexpected failure when you install newer releases. With version-dependent PROGIDs, when you install a newer release, your application will continue to work without failure. If you decide to change the previous version-dependent PROGIDs and use the recent version-dependent PROGIDs in a newer release, you must test your application before putting it into production.  For example, the following scenario shows when applications using version-independent PROGIDs may fail:
    You are running an application that uses SQLXML 3.0 and version-independent PROGIDs, and you decide to install some other software program. This program might install an earlier version of SQLXML. Your application may fail because the version-independent PROGIDS in your application now point to the earlier version of SQLXML, which may or may not have the SQLXML feature that your application is using.

  • On Windows .Net Server 2003 when you create a new virtual directory using the IIS Virtual Directory Management for SQL Server tool, the tool will try to enable the SQLXML isapi (sqlis3.dll) extension in the web service extensions in IIS (if it is not already done). If this process fails, an error message is returnedm and you must do it manually. These are the steps:
    1. Start Internet Information Services (IIS) Manager.

    2. In the Web Service Extensions, click on Add a new Web service extension.

    3. Enter the extension name (any text) in the Extension Name text box.

    4. Click on the Add button and browse for the sqlis3.dll (by default in ...\Program Files\Common Files\System\Ole DB folder).

    5. Check the Set extension status to Allowed check box.

    This will add the ISAP extension and set the its status to Allowed.

  • If for reason you don't want to use SQLXMLOLEDB provider and instead want to use SQLOLEDB provider for SQLXML features, set the SQLXML Version property to "SQLXML.3.0"
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft