SQL Server 2019

Technical 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!

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

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

518 reads

Blogs

T-SQLTuesday 204: Are blogs still relevant?

By

This month’s blogging party is hosted by Jeff Ianucci – his challenge is to...

Are Blogs Still Relevant? I Think They Still Are.

By

As for me, I'll keep writing whenever time permits. I don't expect every post...

Reading Blogs: T-SQL Tuesday #204

By

This is an interesting invitation this month. Jeff Ianucci is a new host, and...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Switching Schemas I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Switching Schemas I

Enforcing Unique Customer Emails When Duplicates Already Exist

By Imran2629

Comments posted to this topic are about the item Enforcing Unique Customer Emails When...

Visit the forum

Question of the Day

Switching Schemas I

I run this query:

SELECT 
 s.name AS schemaname
 , o.name AS objectname
 FROM sys.objects o
 INNER JOIN sys.schemas s ON s.schema_id = o.schema_id
 WHERE o.name = 'Beer'
I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beer
What happens?

See possible answers