Create a SQL Server PolyBase Scale-out Group Using Amazon Web Services
In this article we look at how to create a scale-out SQL Server PolyBase solution on AWS
In this article we look at how to create a scale-out SQL Server PolyBase solution on AWS
Redgate estimate that the savings realized with a monitoring tool could be well over $85,000 / year*. Does your organization understand how a monitoring tool can impact almost every department?
Google Data Studio helps you create comprehensive reports and data visualizations. When combined with CData Connect Cloud, you get instant, cloud-to-cloud access to data from supported SaaS, Big Data and NoSQL sources for visualizations, dashboards, and more. CData Connect Cloud provides a live cloud-to-cloud interface for all your data, making it easy to build reports from […]
Learn how you can get better charting in Azure Data Studio with SandDance.
How Dry Run scripts work, and how they can be used to deliver a single-script release artifact to Staging, verify placeholder substitutions in SQL migration scripts, and simply team code reviews.
SQL Server sequence objects have several properties that control how they behave. Greg Larson explains the options of using SQL Server sequence objects.
The Advent of Code is live, and Steve finds it to be a fun way to take a break during your day.
Introduction In SQL Server 2016, Microsoft introduced a new feature called dynamic data masking, which allows you to mask the values of certain columns and keep that data hidden from certain users, without having to modify your applications. Let's take a look at how SQL Server does data masking, and compare it to the way Gallium Data […]
While relational developers and administrators might always want to use a database, that might not be the case for those that analyze data. Steve suggests you help them see the value of a database platform.
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...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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