SQLServerCentral Editorial

Life Organization

For years, those of us in technology have often worked outside of the core working hours for the rest of our organization. Whether this is being on-call, staying late, or coming in when asked. It's not uncommon for many developers and Ops staff to work 60, 70, or more hours to get things built/deployed/supported for […]

External Article

Join a community like no other at Summit

There's not long until PASS Data Community Summit takes place. There's still time to register for an in-person or online pass, and unlock access to over 300 world-class sessions. Join liked-minded attendees at the year's largest hybrid data platform conference. Get $200 off on the 3-Day Conference pass (in-person) with code REDGATEVIP or 50% off on the 3-Day online pass with code RGVIPONLINE
Register now

Blogs

T-SQL Tuesday #192: SQL Server 2025 Backup Changes

By

I hosted this month, but I decided to put my own entry in as...

Why Databases Still Fascinate Me

By

I get asked a lot about why or how I began working with databases...

Monday Monitor Tips: ServiceNow Integration

By

Earlier this year I visited a customer that was using the Redgate Monitor webhook...

Read the latest Blogs

Forums

Member was not found in the cube when the string

By giles.clapham

Hey, I've not done a cube for many years but I find myself supporting...

Implementing PostgreSQL with Python for Real-Time Logging and Monitoring

By sabyda

Comments posted to this topic are about the item Implementing PostgreSQL with Python for...

Identify a Slipstream Installation

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identify a Slipstream Installation

Visit the forum

Question of the Day

Identify a Slipstream Installation

I get a new SQL Server instance from my build team. How can I tell if the instance was installed using a slipstream installation later?

See possible answers