Articles

External Article

Using SQL Server's Default Trace to Identify Autogrow Events in tempdb

We all know that you should try to size tempdb appropriately, so it doesn’t need to autogrow shortly after starting up SQL Server. It isn’t always easy to do this. Therefore, when you first implement a new server and/or add new databases you should monitor the autogrowth events on tempdb. By monitoring the autogrowth events you can easily determine if you have sized tempdb appropriately.

2018-07-17

2,946 reads

Blogs

Three Ways to Use Snowflake Data in Microsoft Fabric

By

Organizations increasingly want Snowflake and Microsoft Fabric to coexist without duplicating data or fragmenting...

Deploying an Updated Model with SQL Compare 16

By

In a previous post, I deployed a model to a database using SQL Compare...

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022

By

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...

Read the latest Blogs

Forums

Automating Database Cleanup for PostgreSQL Using Python

By sabyda

Comments posted to this topic are about the item Automating Database Cleanup for PostgreSQL...

The Query Optimizer and Page Density

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Query Optimizer and Page...

There Are a Lot of Databases

By Steve Jones - SSC Editor

Comments posted to this topic are about the item There Are a Lot of...

Visit the forum

Question of the Day

The Query Optimizer and Page Density

If I have a fillfactor set to 70%, this reduces my page density to roughly 70%. Does this affect the query plans that the optimizer chooses?

See possible answers