In SQL Server 2005, syslockinfo and sp_lock may return unexpected values, and may return multiple rows where previous versions of syslockinfo and sp_lock returned at most two rows. Also, in order to access information from syslockinfo or execute sp_lock in SQL Server 2005 or later, the user must have VIEW SERVER STATE permission on the server.
In SQL Server 2005 or later versions, sysperfinfo returns a bigint value for the cntr_value column. Modify applications that ...
In SQL Server 2005 or later, data definition language (DDL) statements, such as CREATE INDEX, cannot be performed on the ...
In SQL Server 2005, any subscription rules that generate notifications must insert the notifications into the notification ...
In SQL Server 2005, Notification Services applications cannot have two distributors with the same system name. For each application ...
In SQL Server 2005, syslockinfo and sp_lock may return unexpected values, and may return multiple rows where previous versions ...
In SQL Server 2005, with some exceptions, table hints are supported in the FROM clause of a query only when the hints are ...
In SQL Server 2008, connection strings require a different value for some provider names. The value for the SQL Server Native ...
In SQL Server 2008, global trace flags set by a session take effect in other sessions immediately. Also, some trace flags ...
In SQL Server 2008, Integration Services has changed its application programming interfaces (APIs). To be compatible with ...