>Hi, apologies for posting SQL Server here, but there aren't many participants in the SQL Server forum yet. I suppose I am only making the problem worse by posting here and not there, but hey ho, the works's gotta get done!
>
>I have SQL 6.5 database. The Data and Log share the same device (not my idea). I was copy a very large table into the DB when I got an 'out of log space' error (actually caused by the device being filled by the table).
>
>So I DUMP TRANSACTION dbName WITH NO_LOG, and extended the size of the device and the database by 300 MB. When I look at the database in SQL Enterprise manager, it gives the correct new DB Size as 1600MB, but still shows 0 bytes available for data. Also I cannot add any more records to my very large table as I get more out of space errors.
>
>It has been suggested that I backup the database (2 hours), delete and recreate the database, then restore the data (2 hours again). Does anyone have any quicker suggestions?

It may be that SQL is just confused about the actual records and space... Did you try doing DBCC CHECKDB or DBCC CHECKALLOC? These may take a while to run (could even be about 1/2 hour or so, but still better than 4 hours)