SQL Server 2019

External Article

Introduction to Running SQL Server 2019 on Kubernetes

  • Article

The release of SQL Server 2019 further extends the ability to host SQL Server instances on Linux, including running Docker-based SQL Server images on Kubernetes clusters. This latest release further extends the multi-platform capabilities by allowing for Kubernetes-based deployments of SQL Server Always On Availability Groups, delivering increased level of resiliency. Read on to learn more about the basic characteristics of these deployments!

2019-07-30

SQLServerCentral Editorial

High Prices for High Security

  • Editorial

I was excited to see the new Secure Enclave technology come to Always Encrypted (AE) in SQL Server 2019. I've thought that the way Microsoft implemented the AE technology in SQL Server 2016 was a start and a good step forward, but it had too many restrictions. Kind of like Availability Groups in 2012 and […]

You rated this post out of 5. Change rating

2019-05-30

456 reads

Blogs

T-SQL Tuesday #191: Invitation–Your Favorite String Parsing

By

It’s that time of the month, and I’m late. My apologies. I had a...

Fabric as a Data Mesh Enabler: Rethinking Enterprise Data Distribution

By

For decades, enterprises have approached data management with the same mindset as someone stuffing...

Truncate Table Pitfalls

By

 Truncate Table Pitfalls Truncating a table can be gloriously fast—and spectacularly dangerous when used carelessly....

Read the latest Blogs

Forums

Technological Dinosaurs or Social Dinosaurs?

By Grant Fritchey

Comments posted to this topic are about the item Technological Dinosaurs or Social Dinosaurs?

DBCC CHECKIDENT

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKIDENT

Distributed Availability Group Health: T-SQL and Zabbix

By Pablo Echeverria

Comments posted to this topic are about the item Distributed Availability Group Health: T-SQL...

Visit the forum

Question of the Day

DBCC CHECKIDENT

What is returned as a result set when I run this command without a new seed value?

See possible answers