MS SQL Lost LDF Need To Restore

Hey everyone,

I've run into a fairly big problem. Apparently, the automatic backup has not been working since September, and that backup is of no use to me.

What I'm trying to do is restore the database without using the transaction log file. I don't care about a dirty database or lost data. The data is all I need, and the database structure of course.

I've tried several things.

Right click on the <database> go to tasks->attach-> pick MDF file etc.

Following this guide The only problem is I get a different error message. It doesn't ask a yes no question it just says the file doesn't exist and it can't create the database.

I've tried running it from other SQL management software and removing the LOG file when attaching, and that doesn't work. I tried:

Code:

MS SQL

EXEC sp_detach_db @dbname = <my db name>
EXEC sp_attach_single_file_db @dbname = <my db name>, @physname = <my db mdf file>



and I get the same message pretty much.

I tried this but I can't seem to get the database into emergency mode.

Am at the end of my rope and I really need this up and running ASAP.

Although I'm not sure of the proper syntax for setting a database into emergency mode, I think the last link I provided might do the trick.

I also tried the following:
http://www.spaceprogram.com/knowled...file-on_12.html
But when I get to step 8, the database is not in a suspect mode. When I click on it it says the database is in accessible.

When I right click and click on properties I get:
Quote:
TITLE: Microsoft SQL Server Management Studio Express
------------------------------

Cannot show requested dialog.

------------------------------
ADDITIONAL INFORMATION:

Cannot show requested dialog. (Microsoft.SqlServer.Express.SqlMgmt)

------------------------------

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

------------------------------

Database 'BridgeTrak_Central2' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. (Microsoft SQL Server, Error: 945)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.0194&EvtSrc=MSSQLServer&EvtID=945&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------
I checked the server and there is enough memory and disk space, about 2GB on each drive. Should be plenty for my 32MB database.


It's not my neck on the line but I would like to see my coworker stay here.

If anyone here knows anything about this, that would be great.

MS SQL 2000
Windows Server 2000 SP 4

_Any_ help or suggestions, other than the obvious, make sure backups are working, will be greatly appreciated....

Did I mention greatly appreciated?

I think the issue is that the original database was lost when someone else was trying what I'm trying now. They're very delete happy.

I think they may be SOL... glad it's not me, then again I wouldn't use the delete key without making 100% sure it wouldn't screw things up...I especially wouldn't empty the recycling bin. I probably would have deleted a database already burnt to CD, or burned some to CD....or made sure my backups were working. Messy messy network state, last guy left it in a mess. New network/DBA/ if it's got a network cable attached you're responsible. :S I don't like this new company that much. Too stingy... Dual P2 server?!?!?! Isn't that like, antiquated? No wonder there have been 3 dba/network admins/"if it's got a network cable..." that have left in the past year.