You may encounter an error message that SQL Server 2008 is Error 913. Coincidentally, there are several ways to resolve this issue. We will return to this shortly.
This article is the result of a Skype friend chat – Conversation with one of my valued clients. The problem that many contacted me about was that they couldn’t start the SQL service because the database might not be enabled. I asked for SQL Server ERRORLOG files right below the SQL SERVER Blog – WHERE IS THE ERRORLOG? Various ways to find location ERRORLOG
Here I saw red error information.
2017-04-02 16:38:02.40 spid11s 913, Error: Severity: 17, Status: 6.
2017-04-02 16:38:02.40 spid11s could not find the database with id 3. The database may not have been activated yet or may even be in transition. Run the general query again once you find the database. If you don’t think this particular error is due to a database state change, but you’re still getting this error, contact your primary service provider support. Please take the time to provide the Microsoft SQL Server error log and various other relevant information about the circumstances under which the error occurred.
The above message is intimidating because it is declared. Experts say it’s impossible. to penalize the database id of 3. If you look at the documentation, it’s the labels database id. We know that the model is actually an important system database for running SQL and that further problems with this database can cause SQL startup errors. In my travel bag, the customer didn’t know how the computer was replaced. Well, next detention cell, what do we do? No backups were available. We owned MDF LDF and files. So I tried below./
- I started your current SQL instance with Trace Green 3608 as described on the Books website. We then tried to attach most of the model’s database and got the following error:
Failed to create database
Error: 33401, Severity: 16, FILESTREAM database parameters should not be onincluded in the system databases that model these types.
- We tried unsuccessfully to select system model files from different servers.
- Since there was no append, we cannot trying to restore.
< p>Finally, I asked people to rebuild the system databases, keeping copies of the MDF and LDF files for all databases, on the grounds that this is a backup.
Configure / QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SAPWD= /sqlsysadminaccounts=” built-inadministrators” [email protected]$$word123 /SQLCOLLATION= “SQL_Latin1_General_CP1_CI_AS”
After the above visit is completed, as serious as a clean install with SQL Server. Later, we attached all user directories and created all system objects.
Reference: Pinal Dave (http://blog.SQLAuthority.com)
This blog is a special result of a Skype conversation and also one of my clients. The problem they contacted me about must have been that they couldn’t help you because the SQL service might not be enabled. I tried to share SQL Server ERRORLOG formats usingUsing the blog below. SQL SERVER – where is ERRORLOG? Various ways to find location ERRORLOG
Here is the red related information error I saw.
2017-04-02 16:38:02.40 spid11s 913 , Error: Severity: 16, Status: 6.
2017-04-02 16:38:02.40 spid11s could not find database ID 3. The database may not be activated yet or is in transition. Run the query again when you see the database is available. If you do not believe this error is caused by a database state change and you continue to receive this error, contact your primary transport vendor. For verification, please provide the Microsoft SQL Server Firewood error message and any other relevant information to indicate the circumstances under which the problem occurred.
The above message is scary just because it says it’s possible . t nice database ID = 3. If customers look at the documentation, they will seeyat ID of the database model. We know that a model is a system entry that is required to run SQL, and any database issue will cause problems running SQL. In my case, the user didn’t know how he logged out. Well, the next step that many people should take? There were no backups. We had MDF LDF and also files. So I tried the below./
- I started the SQL instance with trace flag 3608 as described in the online books. We then tried to optionally mount the model database, but got the following error:
Failed to create database
Error: 33401, Severity: 16, unable to set FILESTREAM database options under partition “Relatively”. system databases such as don’t try to restore.
Finally, I asked them to rebuild all system databases, displaying the MDF and LDF report for all Keep databases as a backup.
Configuration /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=”BUILTIN Administrators” /SAPWD= [email protected]$$word123 /SQLCOLLATION= “SQL_Latin1_General_CP1_CI_AS”