tempdb space error

I am hitting a new db installation from Delphi 5 through ODBC.

The 13059 error I get comes up when I open a project I moved to a new
computer.  It says:  General SQL error.  [Microsoft][ODBC SQL Server
Driver][SQL Server]Can't allocate space for object '-385' 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.

I am not even using this database as part of my project, but I am not able to make it bigger and truncating it does no good.  Is there a trick here that I am not seeing?

Thanks
Phil
phillip1Asked:
Who is Participating?
 
chigrikConnect With a Mentor Commented:
Tempdb database is situated on master device by default.
This database contain temporary tables, subqueries and
aggregates with GROUP BY, cursors and so on.
The default size of tempdb is 2 MB. Often it is necessary
to increase this size.

You may remove the tempdb database from master. It is very
good decision for performance and other purposes.

1. Create new device with size of 30-40Mb (tempdev for example)
2. Uncheck "Default device" option for master device.
3. Set "Default device" option for tempdev device.
4. From Enterprise manager (or sp_configure) set tempdb to be in RAM (set value to 1)
5. Stop and restart MSSQLServer service.
6. From Enterprise manager (or sp_configure) set tempdb to not be in RAM (set value to 0)
7. Stop and restart MSSQLServer service.
8. Expand tempdb database to the full size of tempdev device.

Please, be attentive, otherwise you should read the following:
"I've put tempdb in ram and now I can't restart my SQL Server."
http://www.ntfaq.com/ntfaq/sql77.html#sql77

It must helps, if no then read about "Troubleshooting 1105 Error Message"
http://support.microsoft.com/support/SQL/Content/1105err/1105prb.asp?LNG=ENG&SA=PER&FR=0
0
 
Brendt HessSenior DBACommented:
tempdb is a SQL Server internal DB, used for holding temporary tables and other internal purposes by SQL Server (such as temporary tables for Order By clauses)

Try increasing the size of tempdb, or removing the growth restriction (if you set one up for it)

You should also schedule and Shrink Database and Truncate Log activity for the DB on a regular basis.  Enterprise manager makes this simple.


0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.