SQLServerCentral Article

Optimized Plan Forcing with Query Store in SQL Server 2022

In this Article ,  We will delve into the world of Query Store and explore how to use Optimized Plan Forcing to improve performance in SQL Server 2022. We will discuss what it is, how it works, and how it can impact your system's performance.

SQLServerCentral Editorial

A Season of Reflection

As I think about heading into the fall conference season (and seeing so many familiar faces!!), I realize that I'm going to be asking myself a set of familiar questions. Who am I? What skills do I need to improve on in the coming year? Who do I look up to in the community and […]

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