SQL Code Guard v2.8 released
Main change - SCG moved back to .Net framework 3.0 to restore support of SSMS 2008/2008R2
Few small fixes, additional logging, nothing...
2015-05-04
577 reads
Main change - SCG moved back to .Net framework 3.0 to restore support of SSMS 2008/2008R2
Few small fixes, additional logging, nothing...
2015-05-04
577 reads
To use TFS Checking policy the first thing that you must do - is to add policy to your TFS source...
2015-05-11 (first published: 2015-05-02)
6,040 reads
Spoke at 24HOP Russian edition.
Interesting experience.
It is difficult to determine mood of audience if there is no visible audience 🙂
And...
2015-03-18
582 reads
Hi all!
Bad news: SQL Code Guard v2.7 is not working with SSMS from SQL Server 2008R2 (and below).
Good news: I...
2015-03-04
658 reads
Hola!
SqlCodeGuard v2.7 is just released.
To be brief - major changes:1. Added command line utility
2. Added scgallow(issue)/scgignore(issue`)to control which issues should be...
2015-02-17
1,577 reads
Just published new signed build of ExpressProfiler - few nice improvements like advanced search, stay on top window, transparency - just to make...
2015-02-09
613 reads
After installing Community Edition of VS2013 with some additional packages i've noticed that my VS2012 starts failing to start with...
2014-11-15
3,805 reads
Making last changes before sqlsat 311.
By the way, did you ever visited SQL Saturday? No? Why?
SQL Saturday is fun, SQL Saturday...
2014-10-05
634 reads
Sometimes after installing pretty useful addins when starting SSMS you can see error message like "Exception has been thrown by...
2014-09-15
844 reads
Today we released new version of SQL Code Guard, 2.6
Main changes:1. Bug fixing2. Small GUI and usability improvements3. Fixed support...
2014-08-22 (first published: 2014-08-18)
7,112 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