Making Mistakes - Database Weekly (June 1, 2009)
We all make mistakes, even when we are trying to help others. What should you do about it? Steve Jones has a few thoughts on advice online.
We all make mistakes, even when we are trying to help others. What should you do about it? Steve Jones has a few thoughts on advice online.
A legal challenge to the Sarbannes-Oxley act is being heard this fall. Steve Jones doesn't necessarily think this is a bad law.
A legal challenge to the Sarbannes-Oxley act is being heard this fall. Steve Jones doesn't necessarily think this is a bad law.
A legal challenge to the Sarbannes-Oxley act is being heard this fall. Steve Jones doesn't necessarily think this is a bad law.
Introduction In the first article I discussed how the ROW_NUMBER() function can cut down resources spent on queries dealing with versioning. In this article I will discuss how the ROW_NUMBER() function can help when dealing with range requirements. The code samples are available for download. The name of the file is RowCountScenario2-CodeDownload.sql. Scenario 2 – […]
Are you happy with your salary? Are you happy with the way you negotiated it? Steve Jones asks if you might like a different salary structure.
This article from Brian McDonalds shows how to allow style preferences from within SQL Server Reporting Services
You may have a number of jobs scheduled and often there is the need to analyze the data to see which jobs are taking a long time or which job steps are taking a long time. As you add more jobs and overhead to the server these times become even more critical and analyzing the data is key.
We all make mistakes, even when we are trying to help others. What should you do about it? Steve Jones has a few thoughts on advice online.
We all make mistakes, even when we are trying to help others. What should you do about it? Steve Jones has a few thoughts on advice online.
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