2019-03-15
797 reads
2019-03-15
797 reads
When you are setting up a new SQL Server machine you need to determine how big you should make tempdb. To make sure you size tempdb appropriately you should monitor the tempdb space usage. If there are autogrowth events occurring after you have recycled SQL Server than you might want to increase the size of your tempdb data files. If tempdb never uses most of the tempdb space, then you might want to consider decreasing the size of tempdb.
2018-08-21
4,154 reads
Have you ever checked the size of the SQL Server tempdb after restarting SQL Server to find that it's reset? Simon Liew explains this behaviour.
2017-05-31
3,326 reads
TEMPDB doesn't have to be a black box. Know what objects and processes are causing it to bloat in size.
2017-01-30 (first published: 2016-12-29)
2,229 reads
2016-10-07 (first published: 2016-09-20)
1,548 reads
2016-08-29
1,223 reads
2016-07-28
1,191 reads
2016-07-06
1,307 reads
2016-05-03
1,508 reads
2016-04-26
1,260 reads
By Steve Jones
Leave a gate behind you the way you first found it. – from Excellent...
By SQLPals
Fix Slow, Bloated MSDB: Purge Old History And Add Missing Indexes ...
By James Serra
Organizations increasingly want Snowflake and Microsoft Fabric to coexist without duplicating data or fragmenting...
Comments posted to this topic are about the item 25 Years of SQL Server...
Comments posted to this topic are about the item The Decoded Value
Comments posted to this topic are about the item Deploying SQL Server Developer Edition...
In SQL Server 2025, what is returned from this code:
DECLARE @message VARCHAR(50) = 'Hello SQL Server 2025!'; DECLARE @encoded VARCHAR(MAX); SET @encoded = BASE64_ENCODE(CAST(@message AS VARBINARY(1000))); SELECT BASE64_DECODE(@encoded)See possible answers