Achieving More Autonomy At Work
Most of us want more autonomy at work, but it isn't given out without effort. Today Andy Warren has a few thoughts on how to get more freedom from your boss.
Most of us want more autonomy at work, but it isn't given out without effort. Today Andy Warren has a few thoughts on how to get more freedom from your boss.
In this tip, we explore two behaviors for the DAX RANKX function that can lead to incorrect results and discuss workarounds and fixes.
Ready to secure your spot at PASS Data Community Summit? Register by July 26 at the Early Bird rate.
Brent Ozar has his quarterly report on SQL Server versions and SQL Server 2022 isn't being used as much. Does that make sense to you? What versions are you installing?
An interesting approach to schema changes is a creative solution to Steve. He asks if you have other creative solutions you've seen.
PSPO (Parameter Sensitive Plan Optimization) is a SQL Server feature that improves query performance by accepting varied data sizes based on the runtime parameter value(s) specified by the customer. It deals with the situation in which a single cached plan for a parameterized query isn't the best option for all potential incoming parameter values. Non-uniform data distributions exhibit this phenomenon. When using PSPO, SQL Server keeps several execution plans for a single query, each one customized for a particular parameter value. With the help of this feature, numerous execution plans for a parameterized query are generated, each of which is tailored for a certain range of parameter values.
Ready to secure your spot at PASS Data Community Summit? Register by July 26 at the Early Bird rate.
In this article, learn how to query cached query statistics and execution plans for Oracle or SQL Server to identify code that can be optimized to improve performance.
Steve saw a policy on code usage in software development and wondered how many companies have this.
Check out the full details for this year's Pre-Cons and Learning Pathways, and find out why some of our speakers are particularly excited for what’s in store this year. If you’re not already on the mailing list, sign up now and be the first to know all Summit 2023 updates.
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