SQL University: SQL Server Security Architecture - 3rd Party, Some Options
Day 3 of Security Week at SQL University is now in session. You're implementing a third party solution and you...
Day 3 of Security Week at SQL University is now in session. You're implementing a third party solution and you...
Support for SQL Server 2005 expires in April. Should you care? Steve Jones thinks it might not be a big deal for many people.
Wow, it is already February 2011, so here are the February 2011 versions of the SQL Server 2005 Diagnostic Information...
Learn Integration Services from SSIS expert and MVP, Andy Leonard in March. This 5 day class will be held on Mar 21-25, 2011 in Farmville, Virginia.
As a DBA you always followed a practice to back up your database (or take a snapshot of your database) before making any changes so that you can revert to your old database state if something goes wrong. Also to setup a development or test environment you use a backup of your database and restore it in the respective environment. If you are moving to SQL Azure, what would you do in these cases as backup / restore and database snapshots are not supported as of now?
An interesting tutorial for linking SQL Server to a Blackberry device and viewing images.
A series from MVP Jessica Moss designed to help you understand Reporting Services and begin building reports.
Are there things you should know? It seems that we quite often find that others in our profession don't understand the simple things we assume they do. Steve Jones talks about one item in particular: staging servers.
Way back in January, 2008, I wrote a blog post called “Five DMV Queries That Will Make You A Superhero!”...
SEQUENCE is a core new feature of SQL Server 2011 (Denali). It is a more performant, flexible alternative to the INDENTITY attribute. This article introduces sequence and demonstrates how to use it and its performance advantage.
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....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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