The API Bottleneck
Using an API for data access can be good, but it can also be a performance problem if everyone uses it.
2021-11-17
892 reads
Using an API for data access can be good, but it can also be a performance problem if everyone uses it.
2021-11-17
892 reads
The process of building software for others involves lots of decisions. Ensuring that you are making good decisions can impact how others view your final product.
2021-09-27
192 reads
The idea of event driven, rather than tightly coupled architectures is one that Steve thinks data professionals should learn more about.
2021-09-10
299 reads
We use patterns in software development to make things easier. This is especially true in database changes. Steve reminds you that all solutions might have a downside of which you need to understand.
2021-09-08
184 reads
Trying to architect a new database system so that you don't outgrow it is a challenge, but the more you think about early, the better off you will be.
2021-08-30
182 reads
2021-08-21
396 reads
Some organizations see their IT organization as an expense, and not as valuable as it might otherwise be. Steve has a few comments on why this might not be a good idea, or a good place to work.
2021-08-13
280 reads
Steve wishes that Microsoft would follow some of their own advice on SQL Server development in their other software.
2021-08-04
265 reads
Building software in an enterprise is hard, and often, large organizations don't quite know how to do it.
2021-07-12
477 reads
Are hackathons a good way to get a project started? It's not clear to Steve that open ended events are good.
2021-06-14
180 reads
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