Data Driven Subscription Workaround
A guide for getting around the missing data driven subscription feature in Standard editions of Microsoft SQL Server.
A guide for getting around the missing data driven subscription feature in Standard editions of Microsoft SQL Server.
Security is a complex process, one that is becoming more and more important to DBAs all the time. This week Steve Jones wants to know how security is handled for your service accounts.
The Database Engine on the Data Platform departs for Linux. A late arrival but worthwhile, says Phil Factor.
This topic describes options for migrating content from one SQL Server Reporting Services (SSRS) report server to another report server.
Daniel Calbimonte shows how to create an Azure SQL Database with the AdventureworksLT data, and how to import the information into a SQL Server Analysis Services Tabular Model Database.
The Australian Census was a mess, and supposedly some university students build a better version. Steve Jones comments on better coding practices.
This article talks about using the the positive aspects of setting up R in enterprise environment and give instructions on first steps how to do it.
No technology yet invented can in any way allow us to neglect the task of ensuring the security of the database by controlling access. Security must be applied in depth, and the database is designed provide a system that will thwart even the most determined external attack. If it seems a bit complicated at first, that is no longer an excuse now that Rob Sheldon has provided this simple guide for getting started.
Following on from our previous introduction to indexes and partition schemes, we review the distribution schemes used by horizontal partitioning.
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