Editorials

SQLServerCentral Editorial

Why Tools Can Help You Do Your Job

This editorial was originally published on May 18, 2019. It is being re-run as Steve is on holiday. Back in my days as a SQL server DBA, I didn't have many third-party tools at my disposal. I remember having a monitoring tool with licenses for only three or four SQL server instances. Whenever there was […]

You rated this post out of 5. Change rating

2025-01-20 (first published: )

380 reads

SQLServerCentral Editorial

The Weather Outside Is Frightful

Yeah, I know, holidays are over. It snowed about four inches overnight here and it's still coming down a little. You'll forgive me for having that song running through my head. Yesterday morning, before the storm started, we did a check through the house to make sure we were ready for a couple of days […]

You rated this post out of 5. Change rating

2025-01-11

72 reads

Blogs

Want to look at cloud reporting but not sure what the costs will be?

By

Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...

Prime Day Recommendations

By

It’s Prime Day. A few of my recommendations, since I want to do some...

Fabric for Operational Reporting & SQL Endpoint Trap

By

With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments

By Massimo Preitano

Comments posted to this topic are about the item Concurrency and Baseline Control: Level...

Spending Time in the Office

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Spending Time in the Office

Visit the forum

Question of the Day

Multiple Values Inserted

I have this code on SQL Server 2022. What happens when it runs all at once?

DROP TABLE IF EXISTS dbo.Commission
GO
CREATE TABLE dbo.Commission
(id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY
, salesperson VARCHAR(20)
, commission VARCHAR(20)
)
GO
INSERT dbo.Commission
( salesperson, commission)
VALUES
( 'Brian', 12 ),
( 'Brian', 'None' )
GO
 

See possible answers