Database Attach Help!

Due to space issues we had to detach one of our databases. It stopped
working because the drive ran out of space. We have moved the .mdf and the
..ldf to another drive with much more space. When I try to attach I get the
following?
Error 3624
74 transactions rolled forward in database
2006-09-22 12:07:49.53 spid53 SQL Server Assertion: File: <page.cpp>,
line=1920
Failed Assertion = 'IsValidSlot (sid)'.
2006-09-22 12:07:49.53 spid53 Error: 3624, Severity: 20, State: 1.
2006-09-22 12:07:49.53 spid53 Error: 3314, Severity: 21, State: 3
I believe that the transaction lof is corrupt. I there a way to clear the
transaction log and then re-attach?
Any other ideas allso welcome.
Thank you
Paul
I am surprised that you have X transactions rolled forward if you detached the database... You could
try sp_single_file_attach and see if that work with only the mdf file. If not, I suggest you open a
case with MS support.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Paul Glickenhaus" <PaulGlickenhaus@.discussions.microsoft.com> wrote in message
news:A957BF1E-7448-4363-8A23-6F8937C95CF9@.microsoft.com...
> Due to space issues we had to detach one of our databases. It stopped
> working because the drive ran out of space. We have moved the .mdf and the
> .ldf to another drive with much more space. When I try to attach I get the
> following?
> Error 3624
> 74 transactions rolled forward in database
> 2006-09-22 12:07:49.53 spid53 SQL Server Assertion: File: <page.cpp>,
> line=1920
> Failed Assertion = 'IsValidSlot (sid)'.
> 2006-09-22 12:07:49.53 spid53 Error: 3624, Severity: 20, State: 1.
> 2006-09-22 12:07:49.53 spid53 Error: 3314, Severity: 21, State: 3
>
> I believe that the transaction lof is corrupt. I there a way to clear the
> transaction log and then re-attach?
> Any other ideas allso welcome.
> Thank you
> Paul
>