Triggers and System Stored Procedures (System) (Level 4)

Triggers and System Stored Procedures (System) (Level 4)
SQL Server 6.x SQL Server 2000
Returned values were not always correct for text or image columns in either the inserted or deleted tables when either table was used in a CREATE TRIGGER statement. NULL values are returned for text or image column references in the inserted or deleted tables in CREATE TRIGGER.

Expect different results as compared to earlier versions of SQL Server. Remove all references to either the text or image columns of the inserted or deleted tables when used in CREATE TRIGGER statements.

Direct recursion of triggers (the ability of a trigger to call itself) was not supported, but indirect recursion was allowed. Direct trigger recursion is enabled with the RECURSIVE_TRIGGERS option of ALTER DATABASE. Indirect recursion is enabled with the nested triggers configuration option.

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

Server-to-server communication existed between version 4.x and version 6.x servers when initialized by either side. Version 4.x or 6.x servers can communicate with SQL Server 2000 servers. However, server-to-server communication is not supported from SQL Server 2000 servers to 4.x servers.

Expect different results as compared to earlier versions of SQL Server. Upgrade the 4.x server to either SQL Server 6.x or SQL Server 2000

sp_tableoption set option values for user-defined tables, including the use of Insert Row Locking (IRL). The Insert Row Locking (IRL) parameters in sp_tableoption are not supported but have been replaced with complete row-level locking.

Expect different results as compared to earlier versions of SQL Server. Remove all references to IRL actions implemented using sp_tableoption and use the built-in row-level locking of SQL Server 2000 instead. Applications calling sp_tableoption should continue to work properly; the IRL parameters will be ignored.

The @message parameter of xp_readmail was varchar(255). The @message and @query parameters of xp_sendmail were varchar(255). The @message and @query parameters are now varchar(8000).

Expect differences in behavior as compared to earlier versions of SQL Server when using the @message parameter of xp_readmail and the @message and @query parameters of xp_sendmail.


Show: