This is not a bug, but expected behavior.  You said you ran the following command:

BACKUP LOG

Thanks for the informative article! I realize that this article is almost a year old, but I have a few questions that I'm hoping you can help me with.

I...

I've seen similar symptoms occur when deleting rows from a heap table (table with no clustered index). This describes the workaround: http://support.microsoft.com/kb/913399

Kevin

how much acid required in final 3% mixture: 10oz * .03 = .3oz of acid

how much of 10% mixture will it take to make .3oz of acid: x...

We did some pretty intensive benchmark testing and found that our test workload (which included insert/select/update statements as well as bulk inserts, dbcc checkdb, and backups/restores) which was run using...

How about this:

SELECT [name]

FROM master.dbo.sysdatabases

WHERE CAST(DATABASEPROPERTY([name], 'IsOffline') as int) = 1

ORDER BY [name]

Another option would be to turn the database "auto close" option on for each database you want to monitor. Then a "starting up database xxxxx' message will be logged...

It's hard to tell what may have caused it after the fact, but I'd suspect blocking. 

The log files don't show blocking, but you can use sp_who2 and look at...

did you check to see if the insert is being blocked by another spid?

I believe that if your SQL Server was installed with a case-sensitive collation, the login name must be specified with the exact same case as how the Windows user account was...

Maybe there's some confusion due to the fact that pre-SP2 versions of SQL Server are not supported on Windows 2003.

It's not always possible to use TRUNCATE since you may not want to remove all rows, and it's not always feasible to use a TABLOCK hint due to blocking concerns. ...

Not sure if this may apply to you, but there is a bug that prevents space from being released after a delete if the table doesn't have a clustered index.  This...

use

restore

filelistonly from disk = 'D:\Microsoft SQL Server\test1'

to see the logical and physical filenames...

We've seen it not install on all nodes in a clustered environment.  It doesn't give an error message...it says it was successful, but "select @@version" shows 8.00.2039 instead of 8.00.2040...