November 18, 2005 at 5:16 am
I am trying to Input around 45k records using SQL Server with RAM configoration of 1GB [2 slot]. But I am getting thread on the execution of my program as follows in ERRORLOG :-
Error: 1105, Severity: 17,
State: 2 Could not allocate space for object '(SYSTEM table id: -683853068)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full..
During runtime of my java program I am getting the following ERROR on command prompt saying,"----[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Could not allocate space for object '(SYSTEM table id: -7658640)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full.----"
Hope help me to rectify this THREAD
November 21, 2005 at 8:00 am
This was removed by the editor as SPAM
November 22, 2005 at 12:00 am
It looks like either the disk that TempDB is on is full, or the TempDB database is set with fixed size and has filled up.
Check the disk, check the properties of TempDB.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 22, 2005 at 12:42 am
Ya thanks for your massage...
I checked the property of TEMPDB but nothing good has come out
I have free diskspace of 16.1 GB out of 19.5GB total C: Drive space. My HDD Capacity is 80 GB.
So hope you tell me good solutions for the same.
Following is the PROBLEM :-
I am trying to Input around 45k records using SQL Server with RAM configoration of 1GB [2 slot]. But I am getting thread on the execution of my program as follows in ERRORLOG :-
Error: 1105, Severity: 17,
State: 2 Could not allocate space for object '(SYSTEM table id: -683853068)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full..
During runtime of my java program I am getting the following ERROR on command prompt saying,"----[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Could not allocate space for object '(SYSTEM table id: -7658640)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full.----"
November 22, 2005 at 12:56 am
OK, so it's not HDD space.
Please run sp_helpdb 'TempDB' and post the output
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 22, 2005 at 3:17 am
OK I tried to do it in that way. I got the output as follows after run sp_helpdb... once I run the application
tell me what should I do
November 22, 2005 at 3:21 am
I can't see pictures that are on your hard drive. Please post the results of sp_helptext in text.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 22, 2005 at 4:03 am
Name : tempdb
Db size :15216.88 MB
Owner : sa
Db id : 2
Created : Oct 16 2005
Status : [ Status=ONLINE, Updateability=READ_WRITE, UserAccess=MULTI_USER, Recovery=SIMPLE, Version=539, Collation=SQL_Latin1_General_CP1_CI_AS, SQLSortOrder=52, IsAutoCreateStatistics, IsAutoUpdateStatistics ]
Compatibility_level : 80
Filename : C:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf
File Group : PRIMARY
Size : 15581568 KB
MaxSize : Unlimited
Growth :10%
Usage : data only
File Id : 2
Filename : C:\Program Files\Microsoft SQL Server\MSSQL\data\ templog.ldf
File Group : NULL
Size : 512 KB
MaxSize : Unlimited
Growth : 10%
Usage : log only
November 22, 2005 at 4:16 am
Looks like your problem is lack of available hard drive space.
You said you had 16GB free of 19GB on drive C, but the tempdb is on drive C and is already over 15GB in size, and trying to grow by about 1.5GB (grows by 10% of it's size)
Please run the following and post the output
exec master..xp_fixeddrives
I don't know why tempdb is so big, but you can try shinking it.
Restarting sql server will also clean out TempDB, but I would personally leave that as a last resort if all else fails.
Hope that helps
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 22, 2005 at 4:46 am
With my Application I am trying to Convert About 46000 Microsoft EXCEL records to SQL Server ....
During runtime while it reaches around 28% task of conversion it'll show the preoblem. So ofcourse the 'tempdb' is keep increase, I think.
The execution of the command given showing the following result :-
C 1327
D 12204
E 14427
F 9990
G 11104
November 23, 2005 at 2:17 am
So tempdb grows in process of converting ...
Try to insert less records and measure growth of tempdb.
In such cases I'm usualy make such tests:
__________________________________________________________________
Records | Growth| (usualy time - to find how much records optimal)
__________________________________________________________________
1
2
4
8
...
2^n
But 46 thousands records - how can you fill 16 Gb??
Maybe you're explain what kind of records, what kind of conversion you do?
November 23, 2005 at 2:23 am
Converting that many records shouldn't fill TempDB.
Try a restart of SQL (assuming that this is not a production system and you can restart SQL without impacting users) as a restart will empty TempDB. If you're still having problems after, please explain what you're doing to the records and maybe someone can help you optimise the process a bit.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 12, 2006 at 9:43 am
Good topic, but i have a question, is important to commit every xxx of rows inserted? is this Ok? i have a SP that makes a lot of temporary tables (#TABLE), how can i reduce the creation of this kind of tables?
Anyone can send me some scripts to test performance and sql server monitoring?
Thanks for advice...
July 4, 2011 at 9:03 am
Hi, you have clear the drive C:.
July 4, 2011 at 9:14 am
Please note: 6 year old thread.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply