Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

71%
+3 −0
Q&A Is there any justification for having a single tempdb database to be used by all databases on a SQL Server intstances?

Despite the fact that I have programmed against SQL Server for quite a while I did not pay much attention to the tempdb database. This is especially true if application logic is mostly written usin...

1 answer  ·  posted 2y ago by Alexei‭  ·  last activity 2y ago by Derek Elkins‭

#2: Post edited by user avatar Alexei‭ · 2021-10-10T07:16:13Z (over 2 years ago)
added relevant reference
  • Despite the fact that I have programmed against SQL Server for quite a while I did not pay much attention to the `tempdb` database. This is especially true if application logic is mostly written using the ORM instead of stored procedure.
  • However, I have just realized that the SQL Server architecture is pretty strange in that the `tempdb` is a single database shared by all the other databases within the instance. Under heavier loads this can lead to performance issues as mentioned [here](https://www.brentozar.com/blitz/tempdb-data-files/) or [here](https://logicalread.com/3-things-sql-server-tempdb-performance-pd01/).
  • I am wondering about what is the rationale of having a single special database for temporary tables (and other temporary objects to hold "spilled data"). Why not simply use another "space" (e.g. schema) within the database where the query runs? This would certainly ensure a better isolation between databases activity within the same instance.
  • I tried to find the reasons for such a design decision, but perhaps it was decided such a long time ago that nobody argues about it now.
  • Despite the fact that I have programmed against SQL Server for quite a while I did not pay much attention to the `tempdb` database. This is especially true if application logic is mostly written using the ORM instead of stored procedure.
  • However, I have just realized that the SQL Server architecture is pretty strange in that the `tempdb` is a single database shared by all the other databases within the instance. Under heavier loads this can lead to performance issues as mentioned [here](https://www.brentozar.com/blitz/tempdb-data-files/) or [here](https://logicalread.com/3-things-sql-server-tempdb-performance-pd01/).
  • I am wondering about what is the rationale of having a single special database for temporary tables ([and others](https://logicalread.com/sql-server-internals-tempdb/)). Why not simply use another "space" (e.g. schema) within the database where the query runs? This would certainly ensure a better isolation between databases activity within the same instance.
  • I tried to find the reasons for such a design decision, but perhaps it was decided such a long time ago that nobody argues about it now.
#1: Initial revision by user avatar Alexei‭ · 2021-10-10T07:14:22Z (over 2 years ago)
Is there any justification for having a single tempdb database to be used by all databases on a SQL Server intstances?
Despite the fact that I have programmed against SQL Server for quite a while I did not pay much attention to the `tempdb` database. This is especially true if application logic is mostly written using the ORM instead of stored procedure.

However, I have just realized that the SQL Server architecture is pretty strange in that the `tempdb` is a single database shared by all the other databases within the instance. Under heavier loads this can lead to performance issues as mentioned [here](https://www.brentozar.com/blitz/tempdb-data-files/) or [here](https://logicalread.com/3-things-sql-server-tempdb-performance-pd01/).

I am wondering about what is the rationale of having a single special database for temporary tables (and other temporary objects to hold "spilled data"). Why not simply use another "space" (e.g. schema) within the database where the query runs? This would certainly ensure a better isolation between databases activity within the same instance.

I tried to find the reasons for such a design decision, but perhaps it was decided such a long time ago that nobody argues about it now.