Azure SQL Managed Instance – Premium Tier
In case you are not aware Microsoft have now deployed a new change to SQL Managed Instances within the tier types. In certain regions ( shown later) you can...
2021-11-10
149 reads
In case you are not aware Microsoft have now deployed a new change to SQL Managed Instances within the tier types. In certain regions ( shown later) you can...
2021-11-10
149 reads
No doubt there will be times where you need to scale up the actual instance in terms of vCores but also you may want to move across tiers (for...
2021-11-03 (first published: 2021-10-19)
214 reads
With SQL Managed Instance you will need to consider your configuration requirements in terms of core count for the CPU and memory, which we all know that the MIN/MAX...
2021-11-01
114 reads
So in the last blog we confirmed that we could move to SQL MI via some analysis, this is now time to actually do a backup and restore via...
2021-10-12
27 reads
Now that we have a Managed Instance built, the next question is how do we get data across? I will break this up into separate posts but the lesson...
2021-10-07
143 reads
First step login into the Azure portal and find SQL Managed Instance and click create. Yes you can find these tutorials all online but this is my thinking and...
2021-09-14
144 reads
After many years working with different “flavours” of SQL server in Azure from its true PaaS form to SQL server in AKS (Azure Kubernetes Service) it’s time to look...
2021-08-12
198 reads
Just some handy commands to use via kubectl. I found these useful for various reasons so hopefully you will too. Overview of our nodes. Pod information, remember from my...
2021-08-11
48 reads
Last week I created the below with a dummy database and is something that I will do against SQL server but this time that has a persistent volume claim....
2021-08-09
59 reads
So, the point in the previous blog post was to leverage Persistent Volume Claims – PVC for data when using SQL server that it is needed in a stateful...
2021-08-03
20 reads
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers