Instrumenting Code - Database Weekly (Feb 23, 2009)
In the Oracle world, great importance is attached to "instrumenting" your application code. However, it seems not to be an issue that is much discussed in SQL Server. Tony Davis wonders why...
In the Oracle world, great importance is attached to "instrumenting" your application code. However, it seems not to be an issue that is much discussed in SQL Server. Tony Davis wonders why...
Learn how to get deadlock graphs from the SQL Server 2008 default system_health session with Extended Events.
SQL Saturday comes to Pensacola, June 6, 2009. Read on to get more information and sign up for a one day, free training event.
SQL Server has grown from two editions in the v6.5 days to 7 with SQL Server 2008. Why are there so many editions? Steve Jones gives his thoughts.
can undermine server performance. An expert runs various tests to determine how transaction log file size responds to various T-SQL commands.
Question: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? This question was sent to me via email. My reply follows. Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? Databases to be mirrored are currently running on 2005 SQL instances but will be upgraded to 2008 SQL in the near future.
Backup verification is a vital part of a well-designed database maintenance plan and yet some DBAs neglect to do it. Brad McGehee ownders why.
Backup verification is a vital part of a well-designed database maintenance plan and yet some DBAs neglect to do it. Brad McGehee ownders why.
SQL Server has grown from two editions in the v6.5 days to 7 with SQL Server 2008. Why are there so many editions? Steve Jones gives his thoughts.
SQL Server has grown from two editions in the v6.5 days to 7 with SQL Server 2008. Why are there so many editions? Steve Jones gives his thoughts.
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