| title | description | author | ms.author | ms.date | ms.service | ms.topic | monikerRange |
|---|---|---|---|---|---|---|---|
SQLXML Is Not Installed in SQL Server |
SQLXML Is Not Installed in SQL Server |
MikeRayMSFT |
mikeray |
03/14/2017 |
sql |
reference |
=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance] Before [!INCLUDEsql2008-md], SQLXML 4.0 was released with [!INCLUDEssNoVersion] and was part of the default installation of all [!INCLUDEssNoVersion] versions except for [!INCLUDEssExpress]. Starting with [!INCLUDEsql2008-md], 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
[!INCLUDEsql2008-md] 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.