Microsoft, Think DevOps First
Steve has a few issues with the design of the Power BI Service and their format for storing reports.
2019-06-22
405 reads
Steve has a few issues with the design of the Power BI Service and their format for storing reports.
2019-06-22
405 reads
A database script caused a large outage for Salesforce. Steve wonders if you have ideas on how to prevent this type of issue in your environment.
2019-06-21
447 reads
2019-06-11
6,003 reads
A good day for a database administrator (DBA) is a lot like a good airline flight. A lot of excitement in either situation is bad. In a perfect world, a DBA will be productive and not spending most of their time “putting out fires.” (And fires are never a good idea on a flight!)
2019-06-10
As database changes are added to the DevOps pipeline, unit testing of those changes becomes crucial. In this article, Adam Hafner describes unit testing and how it applies to databases.
2019-06-06
The number of times that you have a failure when deploying changes is a good metric to watch.
2025-02-17 (first published: 2019-06-03)
1,307 reads
Establishing coding standards can help remove blockers to understanding code, improving quality and reducing maintenance. Faris Hilmi explains how having consistently formatted code plays a larger role in database development and how Redgate tools can best equip you for the task.
2019-05-30
These are tough times for businesses in the EU. Is the UK going to be in or out? Quite simply, businesses are finding it difficult to plan anything when everything is up in the air, and no one can confirm what will happen next. All of which is making many businesses wary of making a decision to invest in their IT infrastructure. Enter DevOps.
2019-05-21
For application developers it is unthinkable to work without version control. Yet, only 55% of database developers are version controlling their database changes? Mary Robbins provides six reasons why you should version control your database.
2019-05-13
I spend a lot of time showing how to use tools to automate database deployments in support of DevOps. However, the one message that I always try to deliver...
2019-05-13
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