The Danger of Algorithms
What problems occur because of the algorithm chosen to generate data? A new report says that social security numbers in the US can be predicted. Steve Jones has a few warnings about what algoriothms you choose.
What problems occur because of the algorithm chosen to generate data? A new report says that social security numbers in the US can be predicted. Steve Jones has a few warnings about what algoriothms you choose.
This article outlines how to measure resource usage, and use these measurements to develop quality metrics for Big Data applications.
SQLSaturday is a training event for SQL Server professionals and those wanting to learn about SQL Server. This event will be held May 10, 2014. Register while space is available.
There have been some noticable failures of big IT projects this week, but are they always a problem?
Documenting the database is always a challenge, and there are many techniques you can use to help all the people on your team understand what all your tables are used for. David Poole brings us an easy way to implement a framework for documentation.
This week Steve Jones asks about how important reading is to you, and also about what our digital rights might be in a world where we have connected platforms.
Michael Sorens aims to make PowerShell a bit easier to get going with by providing a series of collections of general-purpose one-liners to cover most of what you'll need to get useful scripting done.
Have you received an XML file that must be migrated into a production database? Today’s workshop dives into an ad hoc method of processing relational datasets delivered in an XML file format.
There is a stored procedure that must be run by only one user at a time. In this tip, learn how to prevent multiple users from running the stored procedure at the same time.
The MCM certification program has been abandoned by Microsoft. Steve Jones thinks the material can still be useful for the community.
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