SQLServerCentral Editorial

How can we standardize SQL Server Data Deployments?

Some change requests, such as deploying a new stored procedure or trigger, are relatively easy to manage whereas others, such as data deployments, tend to thwart all attempts at standardization. And yet, there must be a way, and Rodney Landrum believes that DBA-developer co-operation lies at the heart of it.

(2)

You rated this post out of 5. Change rating

2009-12-16

303 reads

SQLServerCentral Editorial

Had this been an actual emergency….

Rodney Landrum has lived through several simulated emergencies and one real one, in the form of Hurricane Ivan. The tests do not adequately prepare you for the real thing. Real emergencies bring tension, exhaustion and hunger pangs. Simulations bring lethargy, pre-determined end times, and warm pizza.

(1)

You rated this post out of 5. Change rating

2009-09-07

181 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