Though it sound strange that why the transaction log grew so much..

you can go ahead an truncate it

backup log databasename with truncate_only and

then shrink the database...

but if you...

yes ..you are right..that was typo ..its sql 2005

top level view

Backup the database with initalize so you have only one bak file all the time

use xp_cmdshell or CLR to copy the file to the destination

Restore with move (force)

for...

PHEW...

System table is gone...

export as much as possible

WTF --> if you have a DB which is important ..dont be lazy to take backup .....

Atleast once a Week for sake

Go to media recovery company and try to see if they can recover the mdf..thats the ONLY HOPE...

HOPING AGAINST HOPE...

might be a more insight

note down the offset value and open scientific calc

select hex and type the offset and change to decimal and divide by 8192 and get the page...

its not in the maintenance plan..

however you can use it using management studio..

Are you taking full backup at night or taking tx backup also

let me add some more

backup log will truncate the log

that means it will reuse the inactive portion of the transaction (few exceptions) log so it will prevent them...

i heard thats not supported sql 2000 on windows vista...

there can be tricks and tweaks to install it..

if you are installing the free version of sql

express is 10 times...

SQL EXpress is a 2005 edition

2000 is not supported on vista

Your system table is corrupt.

Restore from backup or export as much data as possible 🙁

Is is generating stack dumps

one line is good enough

EXEC dbo.sp_stop_job N’jobname'

use this code and check if orphan records goes off

alter database tempdb

REMOVE file locigal_file_name

CHeck if any disk resource is offline for any cluster group .Irresepective if it is a sql group or not