Can you delete tempdb.mdf for Blackberry Enterprise Express?

GalenBolin
GalenBolin used Ask the Experts™
on
The tempdb.mdf MSSQL database for Blackberry is eating up my OS drive. The drive barely has enough space to run. Can this file be deleted or does something else have to be done to reclaim some space?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Commented:
You should not delete tempdb as it is system database used.

Here is a link for best practices around tempdb
http://www.mssqltips.com/tip.asp?tip=1432
is moving it to another drive an option?If its in C:/drive that can be a problem...do you want to move it to another logical drive or you only have one drive?

Author

Commented:
Yes, I have another drive. It is getting full also, but should last until MS Exchange is migrated to another server in a few months.
Exploring SharePoint 2016

Explore SharePoint 2016, the web-based, collaborative platform that integrates with Microsoft Office to provide intranets, secure document management, and collaboration so you can develop your online and offline capabilities.

To clarify on why the tempdb should not be deleted - you should understand what it stores and its purpose.
The tempdb system database is a global resource that is available to all users connected to the instance of SQL Server and is used to hold the following

1.Temporary user objects that are explicitly created, such as: global or local temporary tables, temporary stored procedures, table variables, or cursors.
 2.Internal objects that are created by the SQL Server Database Engine, for example, work tables to store intermediate results for spools or sorting.
 3.Row versions that are generated by data modification transactions in a database that uses read-committed using row versioning isolation or snapshot isolation transactions.
4.Row versions that are generated by data modification transactions for features, such as: online index operations, Multiple Active Result Sets (MARS), and AFTER triggers.

Operations within tempdb are minimally logged. This enables transactions to be rolled back. tempdb is re-created every time SQL Server is started so that the system always starts with a clean copy of the database. Temporary tables and stored procedures are dropped automatically on disconnect, and no connections are active when the system is shut down. Therefore, there is never anything in tempdb to be saved from one session of SQL Server to another. Backup and restore operations are not allowed on tempdb.

Microsoft recommends placing the tempdb on a fast I/O subsystem to get good performance. In this case, try to use RAID 0 disks for tempdb database.
Do not put the tempdb in your c:/ drive....although when you Install SQL Server it will install to its default location which is the folder SQL Server is Installed.
Commented:
NormanMaina's explanation of tempdb is pretty through.  You can certainly shrink tempdb to buy you some time.  Ideally you want to size your database drives to your needs and plan for growth.  As NormanMaina mentioned, moving it away from the system drive is good practice.  The tempdb can eat up I/O and contending with the system page file / slowing down the system drive can cause undesired performance results.

Please see this article on how to shrink tempdb: http://support.microsoft.com/kb/307487
It applies for SQL 2000, 2005

Author

Commented:
Sorry for the long delay, I have been on another assignment. I read the solutions and tried the shrink tempdb. The first method did not work, the other 2 methods were very complicated.

The server in question had not been restarted in 88 days. I said a prayer and rebooted. The full shutdown and restart fixed the problem. The tempdb is under control now.

Thanks for the assistance.

Commented:
The tempdb is used for many purposes and depending on the various applications hosted by your database server, it can grow very quickly.  You should still consider methods to maintain the growth of your tempdb and size your disk capacity to match your requirements.  Restarting the database server may free up your tempdb at the moment but I would not consider your issue to be resolved.  If possible, identify the cause of the tempdb growth and fix the application.  The other is to size your disk capacity to sustain the tempdb demands (preferably on a different drive than your OS).  Good luck.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial