Script level upgrade for database '%1!s!' failed because upgrade step '%2!s!' 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 errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
Schema: the XSD namespace 'http://www.w3.org/2000/10/XMLSchema' is not supported. Please use the namespace 'http://www.w3.org/2001/XMLSchema'. ...
Scoped connection cannot be created because database with name='%{db_name/}', Id='%{db_id/}' is disabled for scoped connections. ...
Scoped connection cannot be created because not all of DatabaseId='%{db_id/}', internalDatabaseName='%{internal_db_name/}' ...
Script level upgrade for database '%1!s!' failed because upgrade step '%2!s!' encountered error %3!s!, state %4!s!, severity ...
Script level upgrade for database '%1!s!' failed because upgrade step '%2!s!' was aborted before completion. If the abort ...
Scripting statistics and histograms can significantly increase the time that is required to generate the scripts. Additionally ...
Scripting statistics and histograms can substantially increase the time required to generate the scripts as well as the size ...
Scripting system objects with dependencies is not supported when AllowSystemObjects is set to false. Error at Urn ='{0}'. ...
Search on full-text catalog '%1!s!' for database ID %2!s!, table or indexed view ID %3!s! with search condition '%4!s!' failed ...