SQL Saturday #59 - New York City
A free day of training in New York City just before Thanksgiving. Come see Steve Jones and Grant Fritchey, along with a number of other great speakers.
A free day of training in New York City just before Thanksgiving. Come see Steve Jones and Grant Fritchey, along with a number of other great speakers.
Steve Jones outlines some ways that you might look to get additional training that can help move your career along.
We have to provide security for our data, and to some extent that means verifying who has access. SQL Server has limited means for doing this other than relying on the OS, but Steve Jones has some ideas on how to make this more secure.
This past week saw the next version of SQL Server, code named Denali, released as a public CTP. Steve Jones comments on the new version.
Transactional Replication is used when DML or DDL schema changes performed on an object of a database on one server needs to be reflected on the database residing on another server. This article provides a step by step guide to setting up transactional replication on SQL Server 2008 R2.
Andy Leonard continues on with his series on TDD. This time he performs some refactoring on his solution.
This Friday Steve Jones talks about database design and specifically asks how you prefer to design triggers.
On Nov 16, 2008, the Luxembourg SQL Server User Group will hold a SQL Server 2008 R2 event in conjunction with Microsoft.
In a previous tip, we did an overview of Extended Events and the different components that make up Extended Events. Now that you know what Extended Events offers, how do you use it to help troubleshoot performance issues? In this tip we take a step by step look at how to implement and use Extended Events.
You can get a look into how SQLServerCentral handles the load of it's database servers with a new tool, and release of reports.
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