HELP Problem with TEMPDB!!

[Jason]

I am having a problem with a newly upgraded SQL 6.5 server that runs our document management systems.

What is causing this error in tembdb? I thought it was the transaction log but Ive already dumped that and I continue to get the problems? How do I fix this permanently?

Error : 1105, Severity: 17, State: 1
2000/09/26 08:19:13.32 spid25 Can't allocate space for object '-804' in database 'tempdb' because the 'system' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.
2000/09/26 08:19:13.32 spid25 Error : 1510, Severity: 20, State: 2
2000/09/26 08:19:13.32 spid25 Sort failed: Out of space or locks in database 'tempdb'
2000/09/26 10:06:42.34 ods Error : 17832, Severity: 18, State: 0
2000/09/26 10:06:42.34 ods Unable to read login packet(s).

Thanks,
Jason Fitch
jason_fitch@shmm.com

[rsp]

Yout TEMPDB most likely ran out of space because it is too small to handle your queries utilizing the tempdb. You need to expand it. (The default is 2mb, which is clearly TOO SMALL in many production environments) See SQL 6.5 unleashed for rules of thumb on setting SIZE OF TEMPDB. In any instance, expand it asap.


------------
Jason at 9/26/00 11:41:42 AM

I am having a problem with a newly upgraded SQL 6.5 server that runs our document management systems.

What is causing this error in tembdb? I thought it was the transaction log but Ive already dumped that and I continue to get the problems? How do I fix this permanently?

Error : 1105, Severity: 17, State: 1
2000/09/26 08:19:13.32 spid25 Can't allocate space for object '-804' in database 'tempdb' because the 'system' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.
2000/09/26 08:19:13.32 spid25 Error : 1510, Severity: 20, State: 2
2000/09/26 08:19:13.32 spid25 Sort failed: Out of space or locks in database 'tempdb'
2000/09/26 10:06:42.34 ods Error : 17832, Severity: 18, State: 0
2000/09/26 10:06:42.34 ods Unable to read login packet(s).

Thanks,
Jason Fitch
jason_fitch@shmm.com

[Craig]

Is it 25% or bigger than your largest database? Have you ensured truncate on checkpoint is on?

Do you know what query is filling it up?


------------
rsp at 9/26/00 2:32:55 PM

Yout TEMPDB most likely ran out of space because it is too small to handle your queries utilizing the tempdb. You need to expand it. (The default is 2mb, which is clearly TOO SMALL in many production environments) See SQL 6.5 unleashed for rules of thumb on setting SIZE OF TEMPDB. In any instance, expand it asap.


------------
Jason at 9/26/00 11:41:42 AM

I am having a problem with a newly upgraded SQL 6.5 server that runs our document management systems.

What is causing this error in tembdb? I thought it was the transaction log but Ive already dumped that and I continue to get the problems? How do I fix this permanently?

Error : 1105, Severity: 17, State: 1
2000/09/26 08:19:13.32 spid25 Can't allocate space for object '-804' in database 'tempdb' because the 'system' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.
2000/09/26 08:19:13.32 spid25 Error : 1510, Severity: 20, State: 2
2000/09/26 08:19:13.32 spid25 Sort failed: Out of space or locks in database 'tempdb'
2000/09/26 10:06:42.34 ods Error : 17832, Severity: 18, State: 0
2000/09/26 10:06:42.34 ods Unable to read login packet(s).

Thanks,
Jason Fitch
jason_fitch@shmm.com