Shulou(Shulou.com)06/01 Report--

Solution: in SQL-Server, after creating a new database with the same name (here assuming Test), stop the database, overwrite the damaged Data.mdf and Test_log.LDF in the Data.mdf and Test_log.LDF under the newly built database directory, and delete the Test_log.LDF file at the same time; start the database service and find the word "doubt" after the database name Test. Never mind, open the SQL built-in query analyzer Perform the following steps: step 1: exec sp_configure 'allow updates',1 RECONFIGURE WITH OVERRIDE / * turn on the switch to modify system tables * / step 2: update sysdatabases set status=32768 where name=' database name' / * set database status * / step 3: DBCC REBUILD_LOG ('database name') 'd:\ database\ Test_Log.LDF') / * rebuild the LDF file * / step 4: update sysdatabases set status=0 where name=' database name' / * reset database state * / step 5: restore database database name WITH RECOVERY / * restore database * / step 6: exec sp_configure 'allow updates',0 RECONFIGURE WITH OVERRIDE / * turn off the switch to modify system tables * / follow this method Should be able to repair normal database access. If the problem persists, the stupidest way is to create another database and export the data from each table in the original database (Test) to the new database table.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.