In the world of SQL Server, script upgrade failures can be a common occurrence when applying service packs or cumulative updates. These failures can lead to issues with the database and prevent the SQL Server instance from starting. In this article, we will explore some common script upgrade failure scenarios and discuss possible solutions.

Scenario 1: CREATE SCHEMA Failed

One common script upgrade failure is the “Script level upgrade for database ‘master’ failed – CREATE SCHEMA failed due to previous errors” error. This error occurs when there are previous errors that prevent the creation of a new schema in the ‘master’ database. To resolve this issue, it is important to identify and fix the previous errors before attempting the script upgrade again.

Scenario 2: Object Already Exists

Another script upgrade failure is the “Script level upgrade for database ‘master’ failed – There is already an object named ‘DatabaseMailUserRole’ in the database” error. This error occurs when there is a conflict with an existing object during the script upgrade process. To resolve this issue, it is necessary to identify and remove the conflicting object before retrying the script upgrade.

Scenario 3: FILESTREAM Feature Initialization Failure

In some cases, the script upgrade failure can be related to the FILESTREAM feature. The error message “FILESTREAM feature could not be initialized” indicates that the Windows Administrator must enable FILESTREAM on the instance using Configuration Manager before enabling it through sp_configure. To resolve this issue, the FILESTREAM feature needs to be properly enabled and configured.

Workaround/Solution

One possible solution to the script upgrade failure is to disable the FILESTREAM feature if it is not being used. The error message “0x80070002” indicates that the system cannot find the specified file, which may be related to file-stream related files/DLLs. By disabling the FILESTREAM feature from the Configuration Manager, it is possible to resolve the script upgrade failure and allow the SQL Server instance to come online.

It is important to note that script upgrade failures can have various causes and solutions may vary depending on the specific scenario. It is recommended to carefully examine the error log entries, take appropriate corrective actions, and consult the SQL Server Books Online for more information on how to resolve specific script upgrade failures.

Have you ever encountered script upgrade issues in SQL Server? Share your experiences and solutions in the comments below!