Eliminating Duplicate Rows using The PARTITION BY clause
The Partition clause in the Row_Number() Over() function is a quick tool for eliminating duplicate rows.
The Partition clause in the Row_Number() Over() function is a quick tool for eliminating duplicate rows.
Today Steve Jones has a poll about the new AlwaysOn feature in SQL Server 2012. Is it worth the upgrade for your company?
How merge replication works, including the impact on the published database. The merge agent, different conflict situations and their resolutions are introduced.
When you are using SSIS, there soon comes a time when you are confronted with having to do a tricky task such as searching for particular connection strings in all your SSIS packages, or checking the execution history of scheduled SSIS jobs. You can do this type of work effectively in T-SQL as Feodor Georgiev explains.
How to change the port number for connections to SQL Server.
A lot has been written about the potential performance benefits of SQL Server data compression; but hard performance data? Not so much.
Today Steve Jones talks about the conflicting demands of home and work and how you can reconcile the requirements of both.
In this tip we cover what CONTROL SERVER is, how to detect its use and a possible way to exploit this permission.
What happens to your indexes during normal database activity?
Is the cloud good for your career? Steve Jones thinks so, and gives you a few reasons you might want to learn more about it.
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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