Question : restoring MSSQL DB from .MDF and .LDF (no 3rd -LOG file)

Hi,

this morning I discovered that it wasn't possible to make Inserts anymore because there was a  File which grew to > 61GB:
D:\sqldata\MSSQL\LOG\SalesLogix-LOG

which took all the HD space.
I then shut down the SQL Server and deleted this file because I thought it only was an error log file.

Now the Enterprise Manager say "SalesLogix (suspect)" - (no items)

D:\sqldata\MSSQL\data\SalesLogix.MDF and
D:\sqldata\MSSQL\data\SalesLogix_log.LDF are still there

I tried to create a new db in the enterprise manager - the .mdf and .ldf where marked with a green cross, but it also expected to find the -LOG file, which was marked with a red X.

I then tried:
sp_attach_db @dbname = 'SLXTA', @filename1='D:\sqldata\MSSQL\data\SalesLogix.MDF' ( 'SLXTA' as a new database)

and it told me:
could not open new database 'SLXTA'. Create Database is aborted.
Device activation error: the physical file name 'D:\sqldata\MSSQL\data\SalesLogix-LOG ' may be incorrect

- although I renamed SalesLogix.MDF to SalesLogix2.MDF it still seams to have hard references to specific paths...
How can I get the DB back up again - with only using the .mdf and .ldf?
What is -LOG anyways? to create a dummy empty one didn't work.

I also tried:
ap_attach_single_file_db but it insisted on the SalesLogix-LOG again:
device activation eroor: the physical file name 'D:\sqldata\MSSQL\data\SalesLogix-LOG ' may be incorrect

Please help or I'll have to look for a new job... :(
Freddy

FOLLOWUP: There is also a backup, 3 weeks old (too old)

Answer : restoring MSSQL DB from .MDF and .LDF (no 3rd -LOG file)

Yes--check out :

http://support.microsoft.com/default.aspx?scid=kb;en-us;253817



It tells you how to use a newer log file against an old MDF.
Random Solutions  
 
programming4us programming4us