DevOps and Continuous Delivery (CI/CD)

Technical Article

Get Ready for DataOps

  • DatabaseWeekly

An emerging discipline called DataOps is taking a page out of the DevOps playbook. The latter is all about accelerating the time to software delivery, and the former about accelerating data flow. And just as DevOps replaces the waterfall method of software delivery, DataOps replaces the waterfall approach of delivering data to the data consumer.

You rated this post out of 5. Change rating

2019-05-03

Technical Article

Musings of a DevOps Data Pro

  • DatabaseWeekly

Continuous delivery and automation are a couple of core concepts of DevOps. As a Data Professional, Derik Hammer has spent countless hours pushing through the resistance of people who feel the data tier should be left out of source control, automated deployments, and who feel the need to make the data tier a separate work stream from applications.

You rated this post out of 5. Change rating

2019-04-05

Blogs

Securing Kubernetes With External Secrets Operator on AWS

By

Here’s a way to centralize management, rotate secrets conveniently without downtime, automate synchronization and...

Save Azure PostgreSQL Backup to Storage

By

This may or may not be helpful in the long term, but since I’m...

The Book of Redgate: What’s Great about Redgate?

By

“I’m sick of hearing about Red Gate.” The first article in the book has...

Read the latest Blogs

Forums

Dynamic T-SQL Script Parameterization Using Python

By omu

Comments posted to this topic are about the item Dynamic T-SQL Script Parameterization Using...

Collation related issues

By LearningDBA

I have read that the collation at the instance level cannot be changed. I...

getting started paas SSAS

By stan

hi our on prem STD implementation of SSAS currently occupies about 3.6 gig of...

Visit the forum

Question of the Day

Multiple Sequences

In SQL Server 2022, I run this code:

CREATE SEQUENCE myseqtest START WITH 1 INCREMENT BY 1;
GO
CREATE TABLE NewMonthSales
  (SaleID    INT
  , SecondID int
 , saleyear  INT
 , salemonth TINYINT
 , currSales NUMERIC(10, 2));
GO
INSERT dbo.NewMonthSales
  (SaleID, SecondID, saleyear, salemonth, currSales)
SELECT
  NEXT VALUE FOR myseqtest
, NEXT VALUE FOR myseqtest
, ms.saleyear
, ms.salemonth
, ms.currMonthSales
FROM dbo.MonthSales AS ms;
GO
SELECT * FROM dbo.NewMonthSales AS nms

Assume the dbo.MonthSales table exists. If I run this, what happens?

See possible answers