Pulling Together
When a co-worker is ill, what should the rest of the office do? How do you handle absences that might extend for weeks or months. Steve Jones comments on the responsibilities of the team.
When a co-worker is ill, what should the rest of the office do? How do you handle absences that might extend for weeks or months. Steve Jones comments on the responsibilities of the team.
When a co-worker is ill, what should the rest of the office do? How do you handle absences that might extend for weeks or months. Steve Jones comments on the responsibilities of the team.
When a co-worker is ill, what should the rest of the office do? How do you handle absences that might extend for weeks or months. Steve Jones comments on the responsibilities of the team.
Steve Jones is looking for some interesting application ideas using SQL Server that can help teach people how to take advantage of features.
We have a new author at SQLServerCentral.com, Muthusamy Anantha Kumar AKA The MAK, who starts a new series on the basics that a DBA needs to know. This installment walks over basic backup and restore.
When databases suddenly stop working, it can be for a number of different reasons. Human error plays a large part, of course, and the DBA needs to know what these various humans are up to. DDL triggers can help alert the DBA to unauthorized tampering with a production system, of course, but DDL triggers can't tell you everything. At some point, you will need to implement your own checks. Randy certainly reached that point!
How much data do you have that's never accessed. Apparently most of it on a network is just stored and never re-examined. Steve Jones comments on a few statistics.
How much data do you have that's never accessed. Apparently most of it on a network is just stored and never re-examined. Steve Jones comments on a few statistics.
How much data do you have that's never accessed. Apparently most of it on a network is just stored and never re-examined. Steve Jones comments on a few statistics.
Table locking hints provide developers much tighter control of their transactions. Look at the benefits and disadvantages of using the NOLOCK and READPAST table hints in SQL Server
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