Building Better Stored Procedures
In a followup, this article includes discussion of more advanced features of using stored procedures.
In a followup, this article includes discussion of more advanced features of using stored procedures.
SQL Server supports partially contained databases. This gives you the option of adding database users with a password inside the database. This makes the database easier to move to another instance or participate in an Always On Availability Group. In this article, Robert Sheldon explains how to work with users in contained databases.
Database encryption is hard, and somewhat controversial. Steve thinks we ought to do a better job of it.
In the next level of the Stairway to SQL Server on Linux learn about the client tools available to connect to your instance.
In this tip we cover how you can implement SQL Server cross database referential integrity using triggers.
Technical debt can cripple software development, much like financial debt hurts individuals and organizations. Steve wants to know if you measure your debt today.
Details discussion on the different isolation levels available in SQL Server
SQL Provision can help organizations ensure compliance with regulations such as HIPAA and SOX. But what exactly are these legislations asking of DBAs and how does this impact the work you do? Robert Sheldon provides an overview of the two US regulations in this four-part series.
Azure provides a number of different methods that can be used in order to implement and configure its resources. Each of the methods differs to some extent in regard to functionality and intended use cases.
Phil Factor argues that very few processes, even in well-established businesses, mimic the dreamy clarity and autonomy of a microservice.
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