Run SQL Command Against Multiple Instances Without CMS
I understand that I can use Central Management Servers to run a T/SQL query against multiple instances at once - can I do this without CMS though?
I understand that I can use Central Management Servers to run a T/SQL query against multiple instances at once - can I do this without CMS though?
A presentation by Steve Jones that talks about the technical basics of what SQL Server is and how it works with some hints about backups, security, and more.
A webinar sponsored by Red Gate Software showing you how easy it can be to source control your database code. Thursday, August 19, 2010 12:00 PM EDT
How can you better keep employees engaged in your company? Keep them happy and hopefully retain them for a long time? Steve Jones has some comments today.
DDL triggers enable us to audit DDL changes but there are a few missing events, design decisions and installation complications.
Performing a LEFT OUTER JOIN in TSQL is easy. The same logic in StreamInsight requires a little more work. In this presentation I show exactly how you can perform a LEFT OUTER JOIN on your event streams. Your browser cannot play this video. Learn how to fix this.
With cloud computing use growing, and SQL Server Azure becoming more popular, Steve Jones wishes this would become a product that the rest of us could deploy.
Today we have a guest editorial from Tim Mitchell that tells you how to turn a bad job into something more.
You need to periodically ascertain if there are any databases in your production environment which are not in SQL Server 2008 Compatibility Level. In this tip we cover the step by step process for setting up a policy to identify databases that are not in SQL Server 2008 Compatibility Level.
Longtime DBA David Poole brings us an interesting situation in involving setting up a user to allow Excel to query data from SQL Server.
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 SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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