In Azure SQL DB, what does “The connection is broken and recovery is not possible” mean?
All it really means is, “Click Execute again, and you will be fine.”
2019-04-15
All it really means is, “Click Execute again, and you will be fine.”
2019-04-15
Azure Database is the PaaS solution for SQL Server databases, on a previous post we have discussed how to create one.On this post, I want to show you how...
The...
2019-04-11
The below image is a beautiful picture, now it could be worse. The red line and the green line could peak at the same time and for a very...
The...
2019-04-11
More and more organizations are moving to the cloud to leverage the key benefits of agility and reduced overall cost. Its likely that at some point in time, your SQL Server will manifest as either of the three implementations in Azure.
2019-03-30
Transitioning to the Platform-as-a-Service model typically implies relinquishing certain degree of control over your computing environment. One of the primary concerns related to this transition is diminished level of transparency providing insights into performance of cloud-resident workloads. Fortunately, with Azure SQL Database, you have a wide range of options that address this concern, allowing you to identify and remediate overwhelming majority of performance-related issues.
2019-01-29
2,366 reads
2019-01-25
649 reads
With Azure SQL Database Hyperscale, databases can quickly auto-scale up to 100TB, eliminating the need to pre-provision storage resources, and significantly expand the potential for app growth without being limited by storage size.
2019-01-10
2,316 reads
Information protection becomes one of the dominant factors that drive modern database design and implementation. This becomes particularly evident when operating in a cloud computing environment, with Azure SQL Database serving as one of the prime examples of this trend. Microsoft delivers relevant features by leveraging several different security-related Azure services. In this article, we will provide an overview of this functionality.
2018-12-04
1,981 reads
2018-10-18
778 reads
Determining the number of DTUs which will help in deciding the service tier for Azure SQL.
2018-09-20
1,028 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