Service Broker Part 2: Why Service Broker
The second part of this series focuses on the advantages of Service Broker over other messaged-based technologies to introduce asynchronous message processing into your database applications.
The second part of this series focuses on the advantages of Service Broker over other messaged-based technologies to introduce asynchronous message processing into your database applications.
Working in a dedicated database model is the ideal. So, what does it take to move from shared development to a dedicated model? Infrastructure costs, merging multiple changes and maintaining an increased estate might be on your list of things to consider before committing to the switch. In this article we show how Redgate tools can ease the transition and new working approach.
Building on the introduction to the SQL used by Cosmos DB in the first article in the series, here you will learn how to handle some of the more...
Aunt Kathi remembers all the SQL Server versions she has worked with over the years.
Fill in another bit of your T-SQL knowledge by learning how to quickly group ranges of contiguous dates without RBAR.
Today we have a guest editorial from Kendra Little that looks at choosing a version control system as you adopt a Database DevOps software development process.
Whenever you’re ready to refresh a test cell with the latest database version, you need a safe way to drop the current set of clones, and the parent image, without losing any unsaved work. Phil Factor provides a PowerShell script that automates this process so it runs in the time it takes to grab a coffee, after which can quickly deploy the new clones.
Security is, or at least should be, the priority for any IT system. In this article, Cynthia Dzikiti discusses the security aspects of ERP systems and some of the techniques used to protect data.
More and more data is being captured and analyzed all the time. At the same time, there are varying expectations of privacy that aren't always shared between the subjects of data and the collectors. Steve has a few thoughts on how this will play out for data professionals.
This week, Brent is demoing SQL Server 2019 features that he's really excited about, and they all center around a theme we all know and love: parameter sniffing.
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....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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