SQL Saturday #262 - Boston
This free event is coming to Boston on March 29, 2014. Grant Fritchey and many others will be speaking, so make sure you register soon while spots are available.
This free event is coming to Boston on March 29, 2014. Grant Fritchey and many others will be speaking, so make sure you register soon while spots are available.
Developers, enamored of the integrated approach to Software Delivery, would like to be able to respond to business need in business time, adding functionality when the need is recognized, instead of 6-9 months later after it's gone through the sclerotic IT purchasing and configuration process.
The practice of continuous software development is growing, with continuous integration, deployment, and delivery being topics that Steve Jones is learning about. Today he talks about delivery.
This is the story of how a free addin for SSMS, SQL Code Guard, was created and joined the Red Gate SSMS Ecosystem project.
A new series on how you can automate partition management and administration. Hugh Scott explains how this technique helps him manage large deletes.
This Friday Steve Jones asks if you build your own mini-me's to help you manage your database systems.
We have a SQL Failover Cluster Instance in our primary data center, and want to implement a second two node Failover Cluster Instance in our secondary data center. A new two node cluster located in our secondary data center was setup, but I could not create a new High Availability Group between the two failover cluster instances. What went wrong?
SQL Saturday is coming to Denmark on March 29, 2014. This a free event of SQL Server training and networking. The full schedule is up (and it's full of great speakers) on the SQL Saturday site and make sure to say hello at the Red Gate booth while you're there.
Allowing your application to generate your SQL can be a really bad decision.
If we want to incorporate big data into our enterprise, it's crucial to know how to integrate it with our existing data.
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