(Un)Common Speed Phreakery
Is there such a thing as too much attention to the performance of SQL? It isn’t only a question of time and inclination, but also of the resilience and flexibility of the code.
Is there such a thing as too much attention to the performance of SQL? It isn’t only a question of time and inclination, but also of the resilience and flexibility of the code.
A Technique to deal with moving data from multiple schemas into one table
Did your company lose data last year? It can be hard to know, especially when even laws designed to ensure breaches are reported have loopholes. Steve Jones thinks this is a bad idea.
This challenge invites you to create a graph/chart using T-SQL
Many times there is the need to restart the SQL Server services, this could be a reboot of the server after patching, service pack installation or due to some other reason. Sometimes we may face issues after the restart for example the SPN is not registered, a database is offline etc... For the solution you can use the below standard SQL Server validation checklist after you restart your SQL services.
Red Gate Software is having another million dollar challenge. If you work for a small software company, or have a software product of your own, read about the challenge.
SQL databases come in all shapes and sizes and schemas. This month, our SQL expert helps with condensing, growing and redesigning databases.
Take a moment and vote on the new SQL Rally logo that will be used for the event next spring.
A short editorial explaining the pitfalls of using search engines as reference for DBA's.
This article will help you to use T-SQL to verify that the Subscribers have the same number of rows of replicated data as the Publisher in transactional replication
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...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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
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