A DBA's Look at the Data Catalog
A data catalog is a way of classifying and adding metadata about the information in your database for compliance purposes. Take a look at how one DBA is using Redgate's Data Catalog.
A data catalog is a way of classifying and adding metadata about the information in your database for compliance purposes. Take a look at how one DBA is using Redgate's Data Catalog.
There is a hero complex for many in IT. Steve provides some advice in how we should look at our workload and our employer's expectations when we consider a new job.
What does Amazon’s Alexa have to do with a wiretapping law from the 1960s? With all the talk about new data privacy legislation, we don’t stop to think about existing laws. Legislation like the GDPR kick-started the way the world views data privacy, and this blog post explores how existing laws are being used in new ways around the globe to enforce similar protection.
Many organisations still run their companies on SQL Server 2008 or 2008 R2. There are many reasons to upgrade, but the most pressing reason is that extended support is running out. In this article, Brian Kelley explains what this means, tells you about some of the features you’ll gain if you upgrade, and provides some options.
Support for SQL Server 2008 and 2008 R2 ended yesterday. Steve has a few thoughts on what you should be thinking about today.
Phil Factor demonstrates the bare essentials of SCA PowerShell scripts that can form the basis for an automated process for database delivery or help improve your current process.
In this article Scott Murray covers some lessons learned over the years when working with SQL Server Reporting Services that he wish he knew when he started with SSRS.
The future of databases is in the cloud. Maybe not for everyone, but it is becoming a trend.
Recently a friend had an issue with their SQL Server as a result of a file change in their SQL Server database. In this short piece, I want to highlight the dangers of making some changes to an online database that might cause an unexpected outage. This is really the same whether you are changing […]
Louis Davidson demonstrates how SQL Prompt can significantly lessen the pain involved in occasional, 'heavyweight' database refactoring processes, such as renaming modules, tables and columns (Smart Rename), or splitting tables (Split Table).
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