DBCC REBUILD_LOG will try to create a tlog for you, but it doesn't care if you have an inconsistent
database. If you can accept inconsistent data, or verify your existent data, this *might* be OK. But
in most cases you prefer a consistent database from an earlier point in time to an inconsistent
database.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ [quoted text, click to view] "Igor A. Chechet" <chechet@etel.ru> wrote in message news:OOU%233kMcFHA.3712@TK2MSFTNGP09.phx.gbl...
> Solution:
>
> 1. Create Database with exact name and mdf-ldf files
>
> 2. Stop MSSQLSERVER service, replace created mdf file with original one
>
> 3. Start MSSQLSERVER service, the database will be in Suspend mode
>
> 4. From Query Analyzer (QA) execute script
>
> use master
>
> go
>
> sp_configure 'allow updates', 1
>
> reconfigure with override
>
> go
>
> 5. From QA execute script
>
> update sysdatabases set status= 32768 where name = '<db_name>'
>
> 6. Restart MSSQLSERVER service, the database will be in Emergency mode
>
> 7. Rebuild Log. From QA execute script
>
> DBCC REBUILD_LOG('<db_name>', '<full name to new log file>'). You got a message - Warning: The log
> for database '<db_name>' has been rebuilt.
>
>
> 8. From QA execute script
>
> Use master
>
> go
>
> sp_configure 'allow updates', 0
>
> Go
>
> 9. Clear from Enterprise Manager on database properties options tab Restrict access checkbox
>
> It works
>
> Igor A. Chechet
>
>