Centrally collect replication conflicts and send an alert
Automatically capture replication conflicts and generate an automated email notification.
2016-02-05 (first published: 2011-10-17)
3,849 reads
Replication
Status de Replicação via E-Mail
Script que envia um relatorio para o seu email com o status de sincronismo de sua replicação.
2011-08-10
329 reads
Monitor SQL Server Replication Jobs
The Replication infrastructure in SQL Server is implemented using SQL Server Agent to execute the various components involved in the form of a job (e.g. LogReader agent job, Distribution agent job, Merge agent job) SQL Server jobs execute a binary executable file which is basically C++ code.
2011-07-11
3,267 reads
2011-07-08
2,080 reads
2011-06-30
2,344 reads
SQL Server Replication: Providing High Availability using Database Mirroring
This white paper describes how to use database mirroring to increase the availability of the replication stream in a transactional environment. The document covers setting up replication in a mirrored environment, the effect of mirroring partnership state changes, and the effect of mirroring failovers on replication. In addition, it describes how to use LSN-based initialization to recover from the failover of a mirrored Subscriber database.
2011-05-17
3,504 reads
Space Impact of Replication Snapshot Agent Job in SQL Server
I have noticed that available disk space on my SQL Server is getting low and I see a number of files getting generated in the replication snapshot folder. Because of these files there is a space issue on my server. Why are these files here and what can I do to resolve this problem?
2011-05-16
2,739 reads
2011-05-05
2,416 reads
Manage and Monitor Identity Ranges in SQL Server Transactional Replication
This article demonstrates how to prevent primary key violation issues in transactional replication.
2011-04-13
2,438 reads
Controlling Growth of a Distribution Database
This article provides a practical example of minimizing the growth of a distribution database.
2011-03-02
2,953 reads
Blogs
Five Ways Redshift Serverless Quietly Eats Your Budget
It is Friday, the queries are running, and nobody is watching the bill. That...
A Career of Memories
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Rethinking Index Maintenance: Why avg_fragmentation_in_percent Is Outdated and What You Should Do Instead
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Forums
What is the Cloud?
Comments posted to this topic are about the item What is the Cloud?
Changing the Schema
Comments posted to this topic are about the item Changing the Schema
Index Fragmentation Explained: Page Splits, Logical Reads, and What to Do
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
Question of the Day
Changing the Schema
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