Having problems importing MDF file (no LDF)

We have a server where the LDF file was deleted by someone. The
software vendor (Platypus) actually recommended doing this. I'm now
stuck with trying to get this DB back up and running.
I tried the methods listed here, but they were not successful. The
failure occurs at the point of rebuilding the LDF file. It ran for
over 15 hours with no effect.
Any ideas here?
Thanks,
DougYou didn't actually mention the "methods listed here", but try
sp_attach_single_file_db.
<nerd1701@.gmail.com> wrote in message
news:1191784420.394668.322780@.o80g2000hse.googlegroups.com...
> We have a server where the LDF file was deleted by someone. The
> software vendor (Platypus) actually recommended doing this. I'm now
> stuck with trying to get this DB back up and running.
> I tried the methods listed here, but they were not successful. The
> failure occurs at the point of rebuilding the LDF file. It ran for
> over 15 hours with no effect.
> Any ideas here?
> Thanks,
> Doug
>|||Only sp_attach_db creates the t-log file if it's not existed too.
--
Ekrem Önsoy
<nerd1701@.gmail.com> wrote in message
news:1191784420.394668.322780@.o80g2000hse.googlegroups.com...
> We have a server where the LDF file was deleted by someone. The
> software vendor (Platypus) actually recommended doing this. I'm now
> stuck with trying to get this DB back up and running.
> I tried the methods listed here, but they were not successful. The
> failure occurs at the point of rebuilding the LDF file. It ran for
> over 15 hours with no effect.
> Any ideas here?
> Thanks,
> Doug
>|||On Oct 7, 4:46 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> You didn't actually mention the "methods listed here", but try
> sp_attach_single_file_db.
> <nerd1...@.gmail.com> wrote in message
>
I tried that as well as the method listed at
http://www.sqlnewsgroups.net/group/microsoft.public.sqlserver.server/topic4869.aspx|||Your software vendor is insane. Is the database in suspect mode or is it
failing to attach period, when using the sp_attach_single_db proc?
<nerd1701@.gmail.com> wrote in message
news:1191784420.394668.322780@.o80g2000hse.googlegroups.com...
> We have a server where the LDF file was deleted by someone. The
> software vendor (Platypus) actually recommended doing this. I'm now
> stuck with trying to get this DB back up and running.
> I tried the methods listed here, but they were not successful. The
> failure occurs at the point of rebuilding the LDF file. It ran for
> over 15 hours with no effect.
> Any ideas here?
> Thanks,
> Doug
>|||On Oct 7, 7:11 pm, "Mike C#" <x...@.xyz.com> wrote:
> Your software vendor is insane. Is the database in suspect mode or is it
> failing to attach period, when using the sp_attach_single_db proc?
>
It fails when trying to do sp_attach_single_db with the error that the
log file is missing or invalid.
Doug|||Basically, you will want to restore from your backup. Even if you find some hack to get this
database into SQL Server, your data is inconsistent. Whatever hack you might find will force some
new log file to be created but the reason it complains as it is is because SQL Server need the log
file to do REDO and UNDO for transactions in order to get a consistent database. So the hack you
might find will leave you with "half performed transactions" i.e., logically inconsistent data (like
an order for a customer that doesn't exist). SQL Server also uses transactions to protect
modifications against meta-data so you risk having a physical corruption as well.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<nerd1701@.gmail.com> wrote in message news:1191858236.871322.193030@.g4g2000hsf.googlegroups.com...
> On Oct 7, 7:11 pm, "Mike C#" <x...@.xyz.com> wrote:
>> Your software vendor is insane. Is the database in suspect mode or is it
>> failing to attach period, when using the sp_attach_single_db proc?
> It fails when trying to do sp_attach_single_db with the error that the
> log file is missing or invalid.
> Doug
>|||On Oct 8, 12:44 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Basically, you will want to restore from your backup. Even if you find some hack to get this
> database into SQL Server, your data is inconsistent. Whatever hack you might find will force some
> new log file to be created but the reason it complains as it is is because SQL Server need the log
> file to do REDO and UNDO for transactions in order to get a consistent database. So the hack you
> might find will leave you with "half performed transactions" i.e., logically inconsistent data (like
> an order for a customer that doesn't exist). SQL Server also uses transactions to protect
> modifications against meta-data so you risk having a physical corruption as well.
>
We tried to restore the backups, but it's asking for a file that
doesn't exist.
For example, we tell it to restore from Wednesday, but it asks for
Friday also. Which doesn't exist.
This isn't my machine directly but belongs to someone else that I'm
trying to help (freely of course :) ).
Doug|||> We tried to restore the backups
I assume this is backups done with the BACKUP DATABASE command?
> but it's asking for a file that
> doesn't exist.
Who is "it"? Use the RESTORE DATABASE command and possibly RESTORE LOG (if you also have log
backups).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<nerd1701@.gmail.com> wrote in message news:1191868968.424106.134380@.k79g2000hse.googlegroups.com...
> On Oct 8, 12:44 pm, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> Basically, you will want to restore from your backup. Even if you find some hack to get this
>> database into SQL Server, your data is inconsistent. Whatever hack you might find will force some
>> new log file to be created but the reason it complains as it is is because SQL Server need the
>> log
>> file to do REDO and UNDO for transactions in order to get a consistent database. So the hack you
>> might find will leave you with "half performed transactions" i.e., logically inconsistent data
>> (like
>> an order for a customer that doesn't exist). SQL Server also uses transactions to protect
>> modifications against meta-data so you risk having a physical corruption as well.
> We tried to restore the backups, but it's asking for a file that
> doesn't exist.
> For example, we tell it to restore from Wednesday, but it asks for
> Friday also. Which doesn't exist.
> This isn't my machine directly but belongs to someone else that I'm
> trying to help (freely of course :) ).
> Doug
>|||On Oct 8, 2:59 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> > We tried to restore the backups
> I assume this is backups done with the BACKUP DATABASE command?
> > but it's asking for a file that
> > doesn't exist.
> Who is "it"? Use the RESTORE DATABASE command and possibly RESTORE LOG (if you also have log
> backups).
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
>
> <nerd1...@.gmail.com> wrote in messagenews:1191868968.424106.134380@.k79g2000hse.googlegroups.com...
> > On Oct 8, 12:44 pm, "Tibor Karaszi"
> > <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> >> Basically, you will want to restore from your backup. Even if you find some hack to get this
> >> database into SQL Server, your data is inconsistent. Whatever hack you might find will force some
> >> new log file to be created but the reason it complains as it is is because SQL Server need the
> >> log
> >> file to do REDO and UNDO for transactions in order to get a consistent database. So the hack you
> >> might find will leave you with "half performed transactions" i.e., logically inconsistent data
> >> (like
> >> an order for a customer that doesn't exist). SQL Server also uses transactions to protect
> >> modifications against meta-data so you risk having a physical corruption as well.
We tried doing the restore through the enterprise manager.
Yes, this was done with the SQL backup manager.
> > We tried to restore the backups, but it's asking for a file that
> > doesn't exist.
> > For example, we tell it to restore from Wednesday, but it asks for
> > Friday also. Which doesn't exist.
> > This isn't my machine directly but belongs to someone else that I'm
> > trying to help (freely of course :) ).
> > Doug- Hide quoted text -
> - Show quoted text -|||> We tried doing the restore through the enterprise manager.
Try the RESTORE command instead. You never know what a GUI tool want to do, and it is also easier to
communicate commands and error messages this way.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<nerd1701@.gmail.com> wrote in message news:1191870417.832070.317830@.19g2000hsx.googlegroups.com...
> On Oct 8, 2:59 pm, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> > We tried to restore the backups
>> I assume this is backups done with the BACKUP DATABASE command?
>> > but it's asking for a file that
>> > doesn't exist.
>> Who is "it"? Use the RESTORE DATABASE command and possibly RESTORE LOG (if you also have log
>> backups).
>> --
>> Tibor Karaszi, SQL Server
>> MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
>>
>> <nerd1...@.gmail.com> wrote in
>> messagenews:1191868968.424106.134380@.k79g2000hse.googlegroups.com...
>> > On Oct 8, 12:44 pm, "Tibor Karaszi"
>> > <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> >> Basically, you will want to restore from your backup. Even if you find some hack to get this
>> >> database into SQL Server, your data is inconsistent. Whatever hack you might find will force
>> >> some
>> >> new log file to be created but the reason it complains as it is is because SQL Server need the
>> >> log
>> >> file to do REDO and UNDO for transactions in order to get a consistent database. So the hack
>> >> you
>> >> might find will leave you with "half performed transactions" i.e., logically inconsistent data
>> >> (like
>> >> an order for a customer that doesn't exist). SQL Server also uses transactions to protect
>> >> modifications against meta-data so you risk having a physical corruption as well.
> We tried doing the restore through the enterprise manager.
> Yes, this was done with the SQL backup manager.
>> > We tried to restore the backups, but it's asking for a file that
>> > doesn't exist.
>> > For example, we tell it to restore from Wednesday, but it asks for
>> > Friday also. Which doesn't exist.
>> > This isn't my machine directly but belongs to someone else that I'm
>> > trying to help (freely of course :) ).
>> > Doug- Hide quoted text -
>> - Show quoted text -
>sql