| title | SQLXML Is Not Installed in SQL Server | Microsoft Docs |
|---|---|
| ms.custom | |
| ms.date | 03/06/2017 |
| ms.prod | sql-server-2014 |
| ms.reviewer | |
| ms.technology | |
| ms.topic | reference |
| ms.assetid | 3dbb4f65-41de-48b8-ad62-47c9d7932de3 |
| author | douglaslMS |
| ms.author | douglasl |
| manager | craigg |
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 when it is available, download it from Install Location for SQLXML SP1.
If an application runs on [!INCLUDEssNoVersion] and requires SQLXML 4.0, and if the computer does not have [!INCLUDEssVersion2005], you must 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] introduces 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 (from Windows Data Access Components, formerly Microsoft Data Access Components) or [!INCLUDEssNoVersion] Native Client OLE DB from [!INCLUDEssVersion2005], these new types will 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. 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.