Additional Articles


External Article

What If You Really DO Need to Shrink a Database?

You’ve heard that shrinking a database is bad because it introduces both external and internal fragmentation, it causes blocking, it causes transaction log growth while it runs, and it’s slow and single-threaded. You understand that if it’s just a matter of 10-20-30% of a database, and the database is only 100-200GB, you might as well just leave the space there, because you’re gonna end up using it anyway.

2020-07-29

Blogs

Implement a RAG Solution Using Azure SQL Database

By

AI and ChatGPT are all the rage these days.  Seems like around every corner...

2024 PASS Data Community Summit Prep

By

Next week is the 2024 PASS Data Community Summit in Seattle. I’ll be traveling...

A New Word: Bye-over

By

bye-over – n.  the sheepish casual vibe between two people who’ve shred an emotional...

Read the latest Blogs

Forums

PASS Summit Time

By Louis Davidson (@drsql)

Comments posted to this topic are about the item PASS Summit Time

database restore chain

By sqlfriend

I have a backup of full, differential and transaction log setup for our database....

Temporary Table Problem

By fk.da

Hello everyone, I hope you can help me. I have a table with measurement...

Visit the forum

Question of the Day

Incremental Statistics

I have run this on SQL Server 2022 for the Sales database:

ALTER DATABASE Sales SET AUTO_CREATE_STATISTICS ON (INCREMENTAL = ON)
I then run this in the Sales database:
USE Sales
GO
CREATE STATISTICS CustomerStats1 ON dbo.Customer (CustomerKey, EmailAddress) WITH INCREMENTAL = OFF
The dbo.Customer table is partitioned. How are statistics created?

See possible answers