Suspicious database solutions

Suspicious solution to the database 1. Change the database to emergency mode: ALTERDATABASE database name SETEMERGENCY2. Change the database to single-user mode: ALTERDATABASE database name SETSINGLE_USER3. Modify the database log to be regenerated, this command checks the allocation, structure, logical integrity, and all objects in the database are not

Suspicious solution to the DATABASE 1. Change the DATABASE to EMERGENCY mode: alter database name set emergency 2. Change the DATABASE to single-user mode: alter database name SET SINGLE_USER 3. Modify the DATABASE log to be regenerated. This command checks the allocation, structure, logical integrity, and all objects in the DATABASE.

Suspicious database solutions

1. Change the database to emergency mode:

Alter database name SET EMERGENCY

2. Change the database to single-user mode:

Alter database name SET SINGLE_USER

3. Modify the Database Log re-generation. This command checks the allocation, structure, and logical integrity of the database and the objects in all databases are incorrect.

When you specify "REPAIR_ALLOW_DATA_LOSS" as the dbcc checkdb command parameter,

The program will check and correct the report. However, these corrections may cause some data loss.

Run: DBCC CheckDB (Database Name, REPAIR_ALLOW_DATA_LOSS)

4. Change the database back to the multi-user mode:

Alter database name SET MULTI_USER

Posted on