Insufficient space in tempdb to hold row versions. Need to shrink the version store to free up some space in tempdb. Transaction (id=%1!s! xsn=%2!s! spid=%3!s! elapsed_time=%4!s!) has been marked as victim and it will be rolled back if it accesses the version store. If the problem persists, the likely cause is improperly sized tempdb or long running transactions. Please refer to BOL on how to configure tempdb for versioning.
Instance name is required to install an instance-specific feature '{0}'. Specify a valid instance name to install this feature. ...
Instances of SQL Server 2005 Notification Services must use SQL Server 2005 databases. Before you can migrate individual ...
Insufficient priveleges to start collection set: '%1!s!'. Only a member of the 'sysadmin' fixed server role can start a collection ...
Insufficient space available in directory {0}. {1}MB is required for this feature, and {2}MB is required for all features ...
Insufficient space in tempdb to hold row versions. Need to shrink the version store to free up some space in tempdb. Transaction ...
Internal %1!s!database snapshot has split point LSN = %2!s!:%3!s!:%4!s! and first LSN = %5!s!:%6!s!:%7!s!. This is an informational ...
Internal error: An attempt was made to set the file position past the end of file for a sequential read or write operation. ...
Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, ...
Internal error: Server stack limit has been reached. Please look for potentially deep nesting in your query, and try to simplify ...