Usage of CTE - Trick with Dates
This article exlores the usage of CTEs as a replacement to cursors in order to generate additional data by applying logic to existing data.
2017-03-03 (first published: 2013-06-18)
37,791 reads
This article exlores the usage of CTEs as a replacement to cursors in order to generate additional data by applying logic to existing data.
2017-03-03 (first published: 2013-06-18)
37,791 reads
The Partition clause in the Row_Number() Over() function is a quick tool for eliminating duplicate rows.
2012-03-02 (first published: 2010-09-22)
144,295 reads
Client data received for processing may have invalid records based on processing requirements. Identifying and dealing with bad records in a specific scenario is the object of this article.
2011-11-22
4,277 reads
This artcle attempts to differentiate between the uses of WITH RECOMPILE and OPTION (RECOMPILE) features.
2011-07-07
8,576 reads
This article attempts to show a practical scenario on improving DB design and performance through row density and compression in Microsoft SQL Server 2008.
2010-11-18
9,223 reads
It is highly recommended that you not rely on system tables in your application as the values and meanings many change between versions. But for an experienced person that digs into the system often and needs quick answers, these system tables may be a great source of information. Suresh Maganti brings us his recent adventure in finding a reliable way to determine the growth factor of a database.
2005-12-06
11,346 reads
Are you looking to move your Oracle databases to SQL Server? You should be and when you convince your management to do so, Microsoft has a tool to help. New author Suresh Maganti of Scalability Experts brings us a look at how this works.
2005-11-28
17,680 reads
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