Version Control - Part 4 - Rolling Back
Part 4 of Steve Jones' series on version control. This article examines how back out your changes from your live systems.
Part 4 of Steve Jones' series on version control. This article examines how back out your changes from your live systems.
Part 1 of Steve Jones series on version control and SQL Server. This article examines how you can work with version control and SQL objects.
In this follow-up to a previous article, Aaron Bertrand reiterates that – while you should never just accept the defaults – you really should think about which options are most applicable to your scenario.
Minion Enterprise can help you with security management in an enterprise.
Automatic UNDO Management isn't voodoo or black magic, although it can seem that way when it isn't clearly understood. How does Oracle decide how many UNDO segments to create at startup, and what is the underlying goal of the process? David Fitzjarrell investigates.
Security alerts and concerns are serious, but that doesn't mean that everyone will treat them that way.
If we only use version control as a way to back up our code then it is pure overhead but actually there are real benefits. We can use source control to write better, cleaner, more readable code.
The Power Query Formula Language (PQFL) is a functional language that drives the Power BI transformations, and allows you to create mashup queries from scratch. In this article, Rob Sheldon demonstrates how to use it in Power BI Desktop to extract data from its source, filter rows, specify the columns, clean the data, and create visualisations.
SET options on stored Procedures work a bit different when compared with ad-hoc queries. These differences in behavior are often overlooked when developing the procedures and generating deployment scripts. This mistake can lead to undesired behavior in the application.
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