upgrading

External Article

Side by Side Upgrade to SQL Server 2022

  • Article

As a SQL Server DBA, the migration of SQL Server from an existing version to the latest version is a usual activity. In today’s cloud-oriented world, many organizations still prefer an on-prem environment; my organization is one of them. There are multiple reasons to keep your data on-prem, like having more privacy and control of the environment. Currently, our major project is to migrate our existing Microsoft SQL Server 2019 to SQL Server 2022. Recently, we completed the POC. Today, let’s discuss the steps of the SQL Server 2022 installation and migration of our databases.

2025-09-24

Blogs

Getting Your Data GenAI-Ready: The Next Stage of Data Maturity

By

I remember a meeting where a client’s CEO leaned in and asked me, “So,...

Learn Better: Pause to Review More

By

If you want to learn better, pause more in your learning to intentionally review.

Azure SQL Managed Instance Next-Gen: Bring on the IOPS

By

If you’ve used Azure SQL Managed Instance General Purpose, you know the drill: to...

Read the latest Blogs

Forums

Azure SQL DBA certification

By ashrukpm

Hello team Can anyone share popular azure SQL DBA certification exam code? and your...

Faster Data Engineering with Python Notebooks: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Faster Data Engineering with Python...

Which Result II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Which Result II

Visit the forum

Question of the Day

Which Result II

I have this code in SQL Server 2022: 

CREATE SCHEMA etl;
GO
CREATE TABLE etl.product
(
    ProductID INT,
    ProductName VARCHAR(100)
);
GO
INSERT etl.product
VALUES
(2, 'Bee AI Wearable');
GO
CREATE TABLE dbo.product
(
    ProductID INT,
    ProductName VARCHAR(100)
);
GO
INSERT dbo.product
VALUES
(1, 'Spiral College-ruled Notebook');
GO
CREATE OR ALTER PROCEDURE etl.GettheProduct
AS
BEGIN
    exec('SELECT ProductName FROM product;')
END;
GO
When I execute this code as a user whose default schema is dbo and has rights to the tables and proc, what is returned?

See possible answers