SQL Server Errors or Failures Error: 902 to Error: 923

 

Error: 902, Severity: 16,
To change the %ls, the database must be in state in which a checkpoint can be executed.

Error: 904, Severity: 16,
Database %ld cannot be autostarted during server shutdown or startup.

Error: 905, Severity: 21,
Database ‘%.*ls’ cannot be started in this edition of SQL Server because it contains a partition function ‘%.*ls’. Only Enterprise edition of SQL Server supports partitioning.

Error: 907, Severity: 16,
The database “%ls” has inconsistent database or file metadata.

Error: 908, Severity: 10,
Filegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available.

Error: 909, Severity: 21,
Database ‘%.*ls’ cannot be started in this edition of SQL Server because part or all of object ‘%.*ls’ is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterpris

Error: 910, Severity: 10,
Database ‘%.*ls’ is upgrading script ‘%.*ls’ from level %d to level %d.

Error: 911, Severity: 16,
Database ‘%.*ls’ does not exist. Make sure that the name is entered correctly.

Error: 912, Severity: 21,
Script level upgrade for database ‘%.*ls’ failed because upgrade step ‘%.*ls’ encountered error %d, state %d, severity %d. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error

Error: 913, Severity: 22,
Could not find database ID %d. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occ

Error: 914, Severity: 21,
Script level upgrade for database ‘%.*ls’ failed because upgrade step ‘%.*ls’ was aborted before completion. If the abort happened during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous

Error: 915, Severity: 21,
Unable to obtain the current script level for database ‘%.*ls’. If the error happened during startup of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the approp

Error: 916, Severity: 14,
The server principal “%.*ls” is not able to access the database “%.*ls” under the current security context.

Error: 917, Severity: 21,
An upgrade script batch failed to execute for database ‘%.*ls’ due to compilation error. Check the previous error message for the line which caused compilation to fail.

Error: 918, Severity: 21,
Failed to load the engine script metadata from script DLL ‘%.*ls’. The error code reported by Windows was %d. This is a serious error condition, which usually indicates a corrupt or incomplete installation. Repairing the SQL Server instance may help resol

Error: 919, Severity: 10,
User ‘%.*ls’ is changing database script level entry %d to a value of %d.

Error: 920, Severity: 20,
Only members of the sysadmin role can modify the database script level.

Error: 921, Severity: 14,
Database ‘%.*ls’ has not been recovered yet. Wait and try again.

Error: 922, Severity: 14,
Database ‘%.*ls’ is being recovered. Waiting until recovery is finished.

Error: 923, Severity: 14,
Database ‘%.*ls’ is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.