Al1


Hi ,

I have a SQL Server 2000 database on my C drive.

Over the weekend my C drive got full due to my transaction log files ballooning up.

At that point none of my users were able to log into their the VB application and enter data.

I freed up some disk space, and then the users were able to log in fine, except for a certain column variable(aggregate) values were negative.

I deattached the DBs and Ldf files and made copies of them on to a test envirnoment. Within the test environment, I ran SQL Query Analyzer with SQL statments that did give me the aggregate values as negative. This matched my VB application values aswell.

I ran

DBCC CHECKDB -- no errors

DBCC DBREINDEX -- no errors

Our programming vendor tells us the DBs are corrupt.

From Error file

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2007-01-30 19:43:56.95 spid52 C:\Program Files\Microsoft SQL Server\MSSQL\Data\tempdb.mdf: Operating system error 112(There is not enough space on the disk.) encountered.

2007-01-30 19:43:56.98 spid52 Error: 1105, Severity: 17, State: 2

2007-01-30 19:43:56.98 spid52 Could not allocate space for object '(SYSTEM table id: -900439724)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full..

2007-02-23 09:56:21.21 spid56 C:\Program Files\Microsoft SQL Server\MSSQL\Data\ActgSQL.mdf: Operating system error 112(There is not enough space on the disk.) encountered.

2007-02-23 09:56:21.24 spid56 Error: 1105, Severity: 17, State: 2

2007-02-23 09:56:21.24 spid56 Could not allocate space for object 'POSInventory' in database 'ActgSQL' because the 'PRIMARY' filegroup is full..

2007-02-23 11:11:09.74 spid56 Error: 1105, Severity: 17, State: 2

2007-02-23 11:11:09.74 spid56 Could not allocate space for object 'POSInventory' in database 'ActgSQL' because the 'PRIMARY' filegroup is full..

2007-02-23 15:50:19.27 spid59 Process ID 53 killed by hostname ORCHID, host process ID 3360.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I thought I had backups but I don t. So now I m in a big bind. Help!!

Any suggestions




Re: Error: 1105, Severity: 17, State: 2

Madhu K Nair


No.. i don't think your database is corrupted. the only thing is that it could not have able to commit the transaction done when there was no space in the desk.. if your statement are not concluded in BEGIN TRAN / COMMIT TRAN.. some data inconsistancy may occur... As such the database may not be corrupted as a whole. This is a common problem when there is no DBA or DBA background person around. You need to keep a track of all backups which u r taking and also TL and TempDb growth etc..

Madhu