Personal Privacy
A new technique to help anonymize medical research data has been developed, and could help with other types of data, but there is an issue.
A new technique to help anonymize medical research data has been developed, and could help with other types of data, but there is an issue.
Sending a large volume of emails can put a strain on a mail relay server. However many people using SQL Server will need to do just that for things like newsletters, mailing lists, etc. Satnam Singh brings us a way to spread out the load by sending newsletters in multiple batches instead of one large process.
In this workbench, Robyn Page provides a gentle introduction to the use of dates in SQL Server. In this new version of her article, it is brought up to date with the newer Datetime features in SQL Server 2005 and 2008.
This year SQLServerCentral is sponsoring another track at the SQL Connections conference in Las Vegas.
In a sequel to his first article on Time Bomb Design, David Poole examines the issues we find between development environments and production ones.
If you will be in London on June 17th, this is an event you do not want to miss.
In Part IV of the Geo-Spatial series, an interactive dashboard is developed to present and interact with the data.
A technique from Bill Nicolich that allows you to target columns by data type for the same custom expression and easily build complex queries.
Are you working too hard? Is it worth it? Steve Jones says that it is not and that you should push back.
Fabiano continues in his mission to describe the major Showplan Operators used by SQL Server's Query Optimiser. This week he meets a star, the Key Lookup, a stalwart performer, but most famous for its role in ill-performing queries where an index does not 'cover' the data required to execute the query. If you understand why, and in what circumstances, key lookups are slow, it helps greatly with optimising query performance.
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
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....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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