An Awesome Job
Life is awesome, and Steve Jones things everyone can find something awesome in their jobs.
Life is awesome, and Steve Jones things everyone can find something awesome in their jobs.
Determining how, and if, SQL Server is using your indexes.
Find out where you can meet the Red Gate team in the US, ask a question, get a custom demo, and maybe a prize as well.
Today Steve Jones talks about learning those advanced features that you don't get the chance to use in your daily work.
Get information about the objects in your database using these ANSI standard, multi-platform views.
Within an instance of SQL Server, the database settings can have a direct effect on the database’s behavior, performance and availability. Sometimes, it is difficult to tie a symptom to a cause, so it is wise to routinely check and record these settings. Before you change the current setting, it pays to understand exactly what it means and the implications of any change.
Networking is one of the best ways to boost your career contacts and help you find a better job. If you are attending the PASS Summit in 2011, take advantage of this two hour seminary from Don Gabor.
An example of how a mathematical problem was converted into T-SQL by evolving a script in iterations.
Today we have a guest editorial from Tim Mitchell. Tim talks about the need to stay motivated in your career after an event ends.
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