Monitoring Transactional Replication – The Distribution Queue
This article looks at the distribution database what information can be obtained for monitoring transactional replication.
2011-02-28
2,431 reads
This article looks at the distribution database what information can be obtained for monitoring transactional replication.
2011-02-28
2,431 reads
This article describes a design pattern for storing “effective dated" changes to fact tables.
2013-10-18 (first published: 2010-12-22)
20,783 reads
Script to get a list of publications an article is in
2010-12-17 (first published: 2010-12-08)
3,786 reads
2010-12-03 (first published: 2010-11-22)
1,711 reads
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.
2010-11-15
2,436 reads
My company uses replication quite extensively across SQL 2000, SQL 2005 and SQL 2008 servers. The problem with using different versions of SQL Server is that the replication options do not always behave the same way. Because of these differences we have stopped using SQL Server Management Studio and Enterprise Manager to setup replication. Also we have taken the time to look at the schema options for replication to make sure the end result is the same for all versions of SQL Server.
2010-10-27
2,218 reads
This article will help you to use T-SQL to verify that the Subscribers have the same number of rows of replicated data as the Publisher in transactional replication
2010-08-05
11,309 reads
Script to setup transactional replication with updatable subscriptions when also using mirroring
2011-06-28 (first published: 2010-06-16)
5,207 reads
Given a tablename and other parameters, this procedure will return a table made of foreign keys and a checksum for each
2010-05-06 (first published: 2010-05-02)
2,025 reads
Replication is a great technology for moving data from one server to another, and it has a great many configuration options. David Poole brings us a technique for scaling out with multiple distribution databases.
2010-03-30
11,248 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