No - unfortunately not.

Management Studio -> Object Explorer -> YourInstance -> YourDatabase -> Management -> SQL Server Logs

Best practices for managing data file growth are:

- manually size your data files to eliminate the...

With a couple of exceptions:

1) if the database was from a prior version of SQL Server and direct upgrade is supported to 2005, then all the upgrade steps need to...

Can you try creating an explicit snapshot of one of the databases to see if that works?

A regular snapshot creates explicit sparse files. The snapshot that DBCC uses is created...

Google search links to http://msdn2.microsoft.com/en-us/library/aa214012(SQL.80).aspx

-b

Specifies that osql exits and returns a DOS ERRORLEVEL value when an error occurs. The value returned to the DOS ERRORLEVEL variable is 1 when the...

Interesting - I wrote the error descriptions document that these MSDN are taken from and it should contain the 'what will repair do section'. For this error, all that will...

Given the structure of your database at present, no object or index has that extent allocated so running repair will not lose any data. Looks like something in the IO...

One more thing that's wrong with this - switching to SIMPLE breaks the log backup chain so you lose the ability to do point-in-time recovery. I have no idea why...

What you can do is export your schema and data out to a SQL 2000 database, as long as you haven't used any 2005 features.

Thanks

I was once forced to marry Kimberly Tripp to get a job with SQLskills.com... 🙂

No - because he would have lost the tail of the log with all the transactions since the last log backup. To get up to the minute recovery, the first...

Very cool. Beers are on you 🙂

ok - so follow the advice from the first response I gave:

In that case, you need to create a dummy database of the same size and layout as the one...

Re-attach the database with the log file and it will be suspect. Backup the tail of the log (by doing a regular log backup and adding WITH NO_TRUNCATE). Then restore...

Ah - in your original post you specifically said you deleted it.

Do you have a backup? Restoring is the way to go if you have one.

ok - so the problem...