Data Types (Level 2)

Installing SQL Server

Installing SQL Server
Data Types (Level 2)
SQL Server 6.x SQL Server 2000
Conversion of binary or varbinary to decimal or numeric was explicit. This conversion is implicit.

Expect different results as compared to earlier versions of SQL Server. Expect conversions of binary or varbinary to decimal or numeric to be implicit. For more information about data type conversions, see CAST and CONVERT. For more information about system-supplied data types, see Data Types.

Conversion of binary or varbinary to smallmoney was not allowed. This conversion is allowed.

Expect different results as compared to earlier versions of SQL Server. Use as appropriate.

Conversion of datetime or smalldatetime to decimal, numeric, float, real, int, smallint, tinyint, money, smallmoney, or bit was not allowed. This conversion is allowed.

Expect different results as compared to earlier versions of SQL Server. Use as appropriate.

Conversion of float or real to binary or varbinary was not allowed. This conversion is allowed.

Expect different results as compared to earlier versions of SQL Server. Use as appropriate.

Conversion of money or smallmoney to char or varchar was implicit. This conversion is explicit.

Expect different results as compared to earlier versions of SQL Server. Expect conversions of money or smallmoney to char or varchar to be explicit.

Conversion of bit to money or smallmoney was not allowed. This conversion is allowed.

Expect different results as compared to earlier versions of SQL Server. Use as appropriate.

sysname data type was varchar(30). sysname data type is nvarchar(128), which allows for 128 Unicode characters.

Expect different results as compared to earlier versions of SQL Server. Expect any columns or local variables defined as sysname to allow Unicode data. For more information about sysname, see Data Types.

No direct support for the nchar, nvarchar, and ntext Unicode data types because maximum storage was 255 bytes for char, binary, varchar, and varbinary data types. The maximum number of bytes that can be stored in char, binary, varchar, and varbinary data types is increased to 8,000. SQL Server 2000 clients fully support the nchar, nvarchar, and ntext data types. SQL Server 6.x clients accessing SQL Server 2000 with these Unicode data types will experience these results:

nvarchar data is returned as varchar and nchar data is returned as char. nvarchar and nchar values longer than 255 double-byte characters are truncated to 255 single-byte characters.

Attempting to access ntext data causes SQL Server to issue a 4004 error. ntext data cannot be sent to version 6.x clients.

char, varchar, binary, and varbinary values longer than 255 bytes are truncated to 255 bytes.

Expect different results as compared to earlier versions of SQL Server. Expect changes in data when accessing SQL Server 2000 data from version 6.x clients. To eliminate these differences, upgrade the clients to SQL Server 2000 client software.

Using CONVERT to convert an empty string to int (CONVERT(int, '')) or float (CONVERT(float, '')) returned a zero. Using CAST or CONVERT to convert an empty string to int (CAST('' AS int)) or float (CAST('' AS float)) returns an error message.

Expect different results as compared to earlier versions of SQL Server.