Undocumented Extended and Stored Procedures
Some useful undocumented extended and stored procedures in SQL Server 2005
Some useful undocumented extended and stored procedures in SQL Server 2005
or our first feature on working DBAs and their lives, we selected Grant Fritchey, the self-styled Scary DBA, who has been so successful in the past year with his books and presentations. How does he manage to pack so much into his life? We sent Richard Morris to find out.
Would you like to have only SQL Server Authentication on your instances? That's the subject of this Friday's poll.
Would you like to have only SQL Server Authentication on your instances? That's the subject of this Friday's poll.
Would you like to have only SQL Server Authentication on your instances? That's the subject of this Friday's poll.
One of the most underused features in SSMS is the additional templates that are available for MDX, DMX, and XMLA....
After several tries I think we finally have it working. If you were unable to attend the last two SQLLunches,...
If your company needs to go through a SOX (Sarbanes–Oxley) audit or any security audit, the DBA has to provide security information to them. If you have purchased third party tools to provide this information that is great. If you don't have third party tools and need to go through many servers to provide this information it can be a hassle and very time consuming. So I put together a script to generate a report that I could just review. The script generates a report of all elevated level accounts and any possible security holes.
Software licensing can be complex and confusing. Even in Windows and SQL Server, where hard limits are not enforced, people have problems determining how they should license software. Steve Jones talks about what vendors could do to help us.
It seems that the ownership of jobs is something that is often overlooked when articles explain
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