The Geek Costume
This Friday Steve Jones has another fun poll. A question on the geek costume that might excite you the most.
This Friday Steve Jones has another fun poll. A question on the geek costume that might excite you the most.
There’s a joke doing the rounds at SQL conferences and seminars: three DBAs walk into a NoSQL bar and leave when they can’t find a table. You may have heard it before, but it made Matt Hilbert sit down and ponder. What’s happening? Is there a division opening up between the newly fashionable NoSQL followers and DBAs? Matt enters the world of NoSQL to investigate.
How to compare two databases and email the results to every one who needs to know
Continuing on with his series on reporting for your SQL Server, David Bird brings together the series with the full package used for building the report.s
What do people do when their job doesn't require a lot of technical skills? Steve Jones has a few thoughts.
This lesson explains how to Clean Data, Explore Data, get Samples of Data, Classify and query a Data Mining Model.
This lesson explains how to Clean Data, Explore Data, get Samples of Data, Classify and query a Data Mining Model.
Salaries for data professionals have risen quite a bit, according to the latest salary survey. That's good for those of us working with SQL Server.
As a society, we have an unrealistic respect for data, especially if it has a decimal point somewhere and uses metric units. We who are in the business of data need to cultivate a renewed interest in the sceptical and rigorous science of statistics: it is too important to leave to 'Data Scientists'. If the data is wrong, or the way we analyse or report it is misleading, much of what we do is pointless.
This metric is a great general indicator of performance problems. High stall times indicate I/O problems, which can be attributed to busy physical disks or queries that return large data sets to the client.
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