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.

Blogs

How to Connect to SQL Server When Nothing Else Works – DAC

By

It's 2 AM. Your phone is going off. Users can't connect to the application,...

Get a Range of Sequence Values: #SQLNewBlogger

By

I discovered a procedure recently that I wasn’t aware of: sp_sequence_get_range. This post looks...

The Agent Era: When “How do I…?” Replaces “Where do I click?”

By

After a year away getting to grips with AI and its application across the...

Read the latest Blogs

Forums

setting an ssis param dynamicaly when the sql agent job runs

By stan

hi i was hoping for a more elegant way of setting a pkg level...

Query compile/runtime issue

By as_1234

I have a plan which in sys.query_store_plan shows: Last_compile_start_time of 2026-04-23 00:13:00.7670000 +00:00 Last_execution_time...

Hiring: Financial SQL Systems Administrator

By Tracy Rivers

Fisher Phillips is looking for a Financial Systems Administrator to help support and improve our financial...

Visit the forum

Question of the Day

Creating a JSON Document II

I want to create a JSON document that contains data from this table:

TeamID TeamNameCity         YearEstablished
1      Cowboys  Dallas       1960
2      Eagles   Philadelphia 1933
3      Packers  Green Bay    1919
4      Chiefs   Kansas City  1960
If I run this code, what document(s) is/are returned?
SELECT json_objectagg( n.city : n.TeamName)
FROM dbo.NFLTeams n;

See possible answers