SQL Server

SQL Server Error Msg 11710 – Argument ‘START WITH’ cannot be used in an ALTER SEQUENCE statement.

SQL Server Error Msg 8989 – %.*ls found %d allocation errors and %d consistency errors in database ‘%ls’.

SQL Server Error Msg 6629 – The result of the column expression for column “%ls” is not compatible with the requested type “XML”. The result must be an element, text node, comment node, processing instruction, or document node.

SQL Server Error Msg 7139 – Length of LOB data (%I64d) to be replicated exceeds configured maximum %ld. Use the stored procedure sp_configure to increase the configured maximum value for max text repl size option, which defaults to 65536. A configured value of -1 indicates no limit, other that the limit imposed by the data type.

SQL Server Error Msg Temporary tables – 10

SQL Server Error Msg 2384 – %sInvalid element occurrence, element ‘%ls’ was found multiple times in the context of element ‘%ls’

SQL Server Error Msg 21711 – Microsoft SQL Server Upload Only Conflict Resolver

SQL Server Error Msg 45199 – This command requires a database encryption scan on database ‘%.*ls’. However, the database has changes from previous encryption scans that are pending log backup. Please wait several minutes for the log backup to complete and retry the command.

SQL Server Error Msg 18826 – Failed to delete rows from the systranschemas table. HRESULT = ‘0x%x’. The rows will be deleted the next time replication executes the stored procedure sp_replcmds.

SQL Server Error Msg 7340 – Cannot create a column accessor for OLE DB provider “%ls” for linked server “%ls”.

SQL Server Error Msg 35252 – The command can only be run on a secondary database. Connect to the correct secondary replica, and retry the command.

SQL Server Error Msg 22977 – Unable to update DDL history information to reflect columns changes applied to the tracked table associated with change table ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.

SQL Server Error Msg 3624 – A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.

SQL Server Error Msg 455 – The last statement included within a function must be a return statement.

SQL Server Error Msg 8917 – Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), index extents %I64d, pages %I64d, mixed extent pages %I64d.

SQL Server Error Msg 35485 – security policy

SQL Server Error Msg 5247 – Repair:  insert a secondary index row based on its base table row.

SQL Server Error Msg 18467 – The login failed for user “%.*ls”. The password change failed. The password does not meet the requirements of the password filter DLL. %.*ls

SQL Server Error Msg 1009 – The keyword DEFAULT is not allowed in DBCC commands.

SQL Server Error Msg 9328 – %sType specification expected, found ‘%ls’.