Attaching a DB gives this error

My database was showing as suspect so I stopped the server, backed up these 2 files & dropped the database.
I recreated a database, stopped the server & copied these 2 files back, it wont attach.
I tried using
sp_attach_db & sp_attach_single_file_db it gives me these errors, any idea?
Server: Msg 9001, Level 21, State 1, Line 1
The log for database 'isgvertusp' is not available.
45 transactions rolled forward in database 'isgvertusp' (6).
Connection Broken
FYI - MDF file size = 57 MB, LOG File size = 6.2 GBFYI- I have checked the existence of Physical files & everything is in place.|||In such case you really should go for a plain simple restore of the database. The actions you took
is not, AFAIK, the documented way to deal with a suspect database. I suggest you indeed restore the
database from a clean backup. You might want to open a case with MS support, but I'm not sure they
can do much for you in this situation.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Prasanna" <sqlemail@.yahoo.com> wrote in message
news:715C565B-D78C-4A59-A995-EDEDEBC1F91F@.microsoft.com...
> My database was showing as suspect so I stopped the server, backed up these 2 files & dropped the
database.
> I recreated a database, stopped the server & copied these 2 files back, it wont attach.
> I tried using
> sp_attach_db & sp_attach_single_file_db it gives me these errors, any idea?
>
> Server: Msg 9001, Level 21, State 1, Line 1
> The log for database 'isgvertusp' is not available.
> 45 transactions rolled forward in database 'isgvertusp' (6).
> Connection Broken
>
> FYI - MDF file size = 57 MB, LOG File size = 6.2 GB
>|||PSS recommends a restore in this case, usually some form of corruption is
involved and the best and supported method of recovery is a restore.
Dylan kruger
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:eriu$UukDHA.2964@.tk2msftngp13.phx.gbl...
> In such case you really should go for a plain simple restore of the
database. The actions you took
> is not, AFAIK, the documented way to deal with a suspect database. I
suggest you indeed restore the
> database from a clean backup. You might want to open a case with MS
support, but I'm not sure they
> can do much for you in this situation.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "Prasanna" <sqlemail@.yahoo.com> wrote in message
> news:715C565B-D78C-4A59-A995-EDEDEBC1F91F@.microsoft.com...
> > My database was showing as suspect so I stopped the server, backed up
these 2 files & dropped the
> database.
> > I recreated a database, stopped the server & copied these 2 files back,
it wont attach.
> > I tried using
> >
> > sp_attach_db & sp_attach_single_file_db it gives me these errors, any
idea?
> >
> >
> > Server: Msg 9001, Level 21, State 1, Line 1
> > The log for database 'isgvertusp' is not available.
> > 45 transactions rolled forward in database 'isgvertusp' (6).
> >
> > Connection Broken
> >
> >
> > FYI - MDF file size = 57 MB, LOG File size = 6.2 GB
> >
>