ETL
Today we have an editorial that was originally published on Aug 31, 2006 as Steve is traveling at DevConnections. It still seems relevant, so answer the poll this week.
Today we have an editorial that was originally published on Aug 31, 2006 as Steve is traveling at DevConnections. It still seems relevant, so answer the poll this week.
Rescheduled for November 8th, 2011 9:00 AM - 10:00 AM PST
Come and learn The Truth about Migration to and Administration for Apache Subversion. CollabNet, Subversion founder and corporate sponsor, and Red Gate Software, number one in SQL source management using any SCM system, want to share five powerful truths about Subversion that will fortify your decision to leave VSS behind.
If you were registered for the original event, please re-register for the new date.
I have transactional replication configured in my production environment. The business team has requested that I do not replicate delete operations on certain articles. In this tip we look at a couple of options to not replicate DELETE commands.
This editorial was originally published on Jan 10, 2007. Steve is at DevConnections, so it is being republished. This piece talks about laptop security when you are working in a public place.
Enabling TDE is simple to do, but it can be more complex when you look to remove the feature from SQL Server. Steve Perry brings you a procedure you can use to help you.
Red Gate is doing some research into SQL testing tools. If you can spare a moment to complete a short survey, or if you're interested in being part of the early access program, please click here.
SQL Server 2008 introduced spatial data support into the database server. This paper describes and discusses the new spatial features in SQL Server Code-Named “Denali” CTP1 and CTP3 that augment existing SQL Server 2008 and SQL Server 2008 R2 spatial functionality.
Today we have an editorial that was originally published on Oct 9, 2006. Steve Jones talks about the issues of turnover, passwords, and security.
The database recovery model plays a crucial role for the recovery of a database. With several DBAs having access to a SQL Server instance there are bound to be changes that are not communicated. In this tip we cover a monitoring solution we deployed at our company to alert the DBAs if a database recovery model is different than what it is expected.
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