Does a missing data file send a database suspect?
Short answer: No
I keep seeing this come up on various forums when people ask what makes a database go suspect...
2010-06-29
2,036 reads
Short answer: No
I keep seeing this come up on various forums when people ask what makes a database go suspect...
2010-06-29
2,036 reads
This blog series will cover several different methods to collect drive information from a Windows server that is running SQL...
2010-06-29
2,653 reads
Sometimes you’ll want to manage reporting services functionality through SQL Server Management Studio (SSMS). This would be the case if...
2010-06-29
2,338 reads
Late night infomercials make some amazing claims. “If you order now you too can cut through a cinderblock wall and...
2010-06-29
1,507 reads
This year at SQL Saturday #28 we will be featuring a User Group Booth alongside the Sponsor booths. The User Group...
2010-06-29
1,566 reads
This is my third in a series of checklists that I am putting together for a new book designed for...
2010-06-29
2,958 reads
Here’s the editorial for SSC today and while it’s a humorous story about asking for donuts and getting a free...
2010-06-29
1,426 reads
The Trade Deadline Must be Drawing Near
Okay, so there is no trade deadline in SQL Server like there is in...
2010-06-29
2,137 reads
After 10 Years, a Move Closer to School and Work
Wow, how moving house interrupts life. I can appreciate we have...
2010-06-28
513 reads
2010-06-28
686 reads
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
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