A Hazard of Using the SQL Merge Statement
The SQL MERGE statement can make your DML querying more efficient but you need to take care or you may get burned
The SQL MERGE statement can make your DML querying more efficient but you need to take care or you may get burned
Data could be the way that more decisions are made, separating the competent from the incompetent in the future. Steve Jones isn't sure this is the best way to make decisions if we don't include a human element in the decision process.
Join top business intelligence and analytics experts in Chicago April 10-12 for 60+ sessions on the best practices, prescriptive guidance, and strategic vision you need to get the most from your data. Use code BACSSC to save $250 today!
Normally, the query Optimiser won't consider 'bushy' plans, where both operands to a join operator could be intermediate results from other joins. This means that it won't produce good query plans for some types of query. Hints, by themselves won't do it. More powerful magic is required.
The goal of this article to show how to get unique transactions per client per month from the data set containing multiple transactions per client per month.
The release of an extensive salary report for Information Technology shows some good trends in it for 2013.
Join us at SQL Saturday Boston on April 6th. SQL Saturday is a free training event for SQL Server Professionals and those wanting to learn more about SQL Server.
n a database I currently support, the application makes use of db_datareader and db_datawriter to give permissions to the tables. In a different database, it's even worse as the application uses db_owner. We're adding new tables to both databases and we don't want the application to have access to these tables. How can I deal with the use of these three roles?
A new idea from a small startup may revolutionize the way that you search for data.
Before adopting NoSQL for a commercial application that needs consistency and durability, you need to be satisfied that the product actually provides all those niceties that the user of relational database systems take for granted.
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