The Code Freeze
Today Steve discusses code freezes, those times when you don't allow changes to be made by developers.
2024-04-10
226 reads
Today Steve discusses code freezes, those times when you don't allow changes to be made by developers.
2024-04-10
226 reads
In software development the concept of feature toggles are used to selectively turn on and off features. They are, for example, used to restrict some newly introduced features to a select group to see how these features work. While this concept has been long used for user-facing application code, it is also a practice that is useful for database code.
2024-03-22
Sometimes you need to completely change your software, perhaps on a new platform. Steve has a few thoughts on this drastic action.
2024-03-20
171 reads
Code reviews are a good way to not only improve your quality, but also raise the skill level of your staff.
2024-02-28
243 reads
There are a number of ways to run SQL Server for free (or low cost) for development. Read a bit about how to do this.
2024-02-23
7,650 reads
At Redgate, the teams change every year and Steve has a few reasons why this is good.
2024-02-12
190 reads
When it comes to building websites, how you work with your database can make a huge difference in how well your site runs. That's especially true if you're using Django, a popular tool for making websites with Python. Django comes with something called an Object-Relational Mapping (ORM) layer, which is a fancy way of saying […]
2024-01-26
5,119 reads
Learning to make decisions and then get work done is important to Steve. Read his thoughts today on many of the decisions software teams need to make.
2024-01-24
183 reads
Today Steve has a few stories of how he's fixed poor programming practices and asks you to share your own.
2024-01-03
349 reads
Speed of delivery and protecting data can often feel incompatible, but there are industry-proven database DevOps practices that bring them together in harmony.
Across each of these five key practices, there’s a theme of removing barriers and cognitive load for teams; but crucially, they are also putting safeguards in place to reduce the risks to production environments.
2023-11-06
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
It is Friday, the queries are running, and nobody is watching the bill. That...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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