Skip to content

Latest commit

 

History

History
44 lines (33 loc) · 2.65 KB

File metadata and controls

44 lines (33 loc) · 2.65 KB
title SQLXML Is Not Installed in SQL Server | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql-non-specified
ms.prod_service database-engine, sql-database
ms.service
ms.component sqlxml
ms.reviewer
ms.suite sql
ms.technology
ms.tgt_pltfrm
ms.topic reference
ms.assetid 3dbb4f65-41de-48b8-ad62-47c9d7932de3
caps.latest.revision 17
author douglaslMS
ms.author douglasl
manager jhubbard
ms.workload Inactive

SQLXML Is Not Installed in SQL Server

[!INCLUDEappliesto-ss-asdb-xxxx-xxx-md] Before [!INCLUDEssKatmai], SQLXML 4.0 was released with [!INCLUDEssNoVersion] and was part of the default installation of all [!INCLUDEssNoVersion] versions except for [!INCLUDEssExpress]. Starting with [!INCLUDEssKatmai], the latest version of SQLXML (SQLXML 4.0 SP1) is no longer included in [!INCLUDEssNoVersion]. To install SQLXML 4.0 SP1, download it from Install Location for SQLXML 4.0 SP1.

If an application runs on [!INCLUDEssNoVersion] and requires SQLXML 4.0, you have to download and install SQLXML 4.0 SP1.

SQLXML 4.0 SP1 Behavior with New Data Types Using SQLOLEDB and SQL Server Native Client OLE DB Provider

[!INCLUDEssKatmai] introduced the following data types, which developers using SQLXML might want to use:

  • Date

  • Time

  • DateTime2

  • DateTimeOffset

When using SQLXML 4.0 SP1 with either SQLOLEDB or [!INCLUDEssNoVersion] Native Client OLE DB from [!INCLUDEssVersion2005], these types appear as strings to a developer. SQLXML 4.0 SP1 will enable these four new data types as built-in scalar types when used with [!INCLUDEssNoVersion] Native Client OLE DB Provider 11.0 or later. Until you download SQLXML 4.0 SP1, mapping these types to non-string types might cause truncation of some data. For example, mapping DateTime2 to xsd:date will cause data to be truncated to the [!INCLUDEssVersion2005] DateTime precision of 3.33 milliseconds.

See Also

SQLXML 4.0 Programming Concepts