SQL Server 2008 Capture DML Changes Using Change Data Capture
In this article Ashish continues to explore the Change Data Capture feature in SQL Server 2008. This article demonstrates how to track DML changes
In this article Ashish continues to explore the Change Data Capture feature in SQL Server 2008. This article demonstrates how to track DML changes
This refresher on SQL Server examines when to use a database as well when not to, along with some of the key terms used with SQL Server.
As Information Technology workers become more wired, with more demands, and less benefits, should they consider unionizing.
More and more technology workers are being asked to sign non-compete agreements as a condition of their employment. But is that fair? Steve Jones has a few thoughts.
Monitoring your SQL Server Agent jobs is important to ensuring that all of the automation you have created on your server is working correctly. Thomas LaRock brings us another article on Operations Manager and its integration with SQL Server.
Database Mirroring was released with SQL Server 2005 and is becoming a popular choice for a failover solution. One of the big issues with Database Mirroring is that the failover is tied to one database, so if there is a database failure the mirrored server takes over for this one database, but all other databases remain functional on the primary server.
Where is the dividing line between work time and personal time? As more and more employees get new phones, such as the Blackberry and iPhone, is the line becoming too blurred? Are there legal implications?
Where is the dividing line between work time and personal time? As more and more employees get new phones, such as the Blackberry and iPhone, is the line becoming too blurred? Are there legal implications?
Where is the dividing line between work time and personal time? As more and more employees get new phones, such as the Blackberry and iPhone, is the line becoming too blurred? Are there legal implications?
As Information Technology workers become more wired, with more demands, and less benefits, should they consider unionizing.
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