Data lineage is a component of modern data management that helps organizations understand the origins, transformations, and movement of their data. It is like a road map that shows us where our data has been, how it has changed, and where it is going, just like tracking the journey of a package:
Learn how to get started working with SMO and PowerShell.
Learn how to get started working with SMO and PowerShell.
Learn how to get started working with SMO and PowerShell.
In the fourth level of this series, we will examine how you can use the scripting classes to create the code to manage your SQL Server instances and databases.
In this level you will learn about the SQLServer PowerShell module that ships with modern versions of SSMS.
This week I had the opportunity to join many of the U.S.-based Redgaters in Austin to talk about 2024 plans, hear from the product teams, and have some much-needed fellowship. One thing was particularly clear as I listened to various leaders and product managers – the customer drives everything we do. And I have to […]
How do you determine if you're at the top of your profession? Andy Warren has a few thoughts today.
Buy your on-demand ticket today to get access to hundreds of high-quality sessions across all 5 tracks at PASS Data Community Summit 2023. It’s a great way of learning at your leisure if you weren’t able to join us in person last year.
On-demand access is available for non-attendees to purchase for $1295. This will grant you access to all session recordings until November 17, 2024. Click here to buy.
MongoDB is a document database. As such, the data is stored as individual documents. A document is a data structure made up of one or more field/value pairs.
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