inilah yang biasanya saya lakukan ketika saya memiliki publikasi yang kacau.
itu agak jelek tetapi telah bekerja untuk saya pada banyak kesempatan di lingkungan yang berbeda. apa yang menyebabkannya? yang kadang-kadang sulit untuk mencari tahu, yang terbaik kadang-kadang untuk memulai dari awal, tapi bahkan untuk itu Anda perlu untuk membersihkan all
yang residuals
dari publikasi saat ini yang rusak.
hanya untuk memasukkannya ke dalam konteks:
Ini yang saya lihat dari monitor replikasi:
dan ketika saya menggunakan monitor replikasi saya sendiri menggunakan T-SQL :
DECLARE @cmd NVARCHAR(max)
DECLARE @publisher SYSNAME, @publisher_db SYSNAME, @publication SYSNAME, @pubtype INT
DECLARE @subscriber SYSNAME, @subscriber_db SYSNAME, @subtype INT
DECLARE @cmdcount INT, @processtime INT
DECLARE @ParmDefinition NVARCHAR(500)
DECLARE @JobName SYSNAME
DECLARE @minutes INT, @threshold INT, @maxCommands INT, @mail CHAR(1) = 'N'
SET @minutes = 60 --> Define how many minutes latency before you would like to be notified
SET @maxCommands = 80000 ---> change this to represent the max number of outstanding commands to be proceduresed before notification
SET @threshold = @minutes * 60
IF OBJECT_ID ('TEMPDB..#Replication_Qu_History') IS NOT NULL
DROP TABLE #Replication_Qu_History
IF OBJECT_ID ('TEMPDB..##PublicationInfo') IS NOT NULL
DROP TABLE ##PublicationInfo
IF OBJECT_ID ('TEMPDB..#PublisherInfo') IS NOT NULL
DROP TABLE #PublisherInfo
IF OBJECT_ID ('TEMPDB..##SubscriptionInfo') IS NOT NULL
DROP TABLE ##SubscriptionInfo
SELECT * INTO #PublisherInfo
FROM OPENROWSET('SQLOLEDB', 'SERVER=(LOCAL);TRUSTED_CONNECTION=YES;'
, 'SET FMTONLY OFF EXEC distribution.dbo.sp_replmonitorhelppublisher')
SELECT @publisher = publisher FROM #PublisherInfo
SET @cmd = 'SELECT * INTO ##PublicationInfo FROM OPENROWSET(''SQLOLEDB'',''SERVER=(LOCAL);TRUSTED_CONNECTION=YES''
,''SET FMTONLY OFF EXEC distribution.dbo.sp_replmonitorhelppublication @publisher='
+ @publisher + ''')'
--select @cmd
EXEC sp_executesql @cmd
SELECT @publisher_db=publisher_db, @publication=publication, @pubtype=publication_type FROM ##PublicationInfo
SET @cmd = 'SELECT * INTO ##SubscriptionInfo FROM OPENROWSET(''SQLOLEDB'',''SERVER=(LOCAL);TRUSTED_CONNECTION=YES''
,''SET FMTONLY OFF EXEC distribution.dbo.sp_replmonitorhelpsubscription @publisher='
+ @publisher + ',@publication_type=' + CONVERT(CHAR(1),@pubtype) + ''')'
--select @cmd
EXEC sp_executesql @cmd
ALTER TABLE ##SubscriptionInfo
ADD PendingCmdCount INT NULL,
EstimatedProcessTime INT NULL
SELECT *
FROM #PublisherInfo
SELECT *
FROM ##SubscriptionInfo
SELECT *
FROM ##PublicationInfo
Anda dapat melihat 2 baris pada kotak terakhir di bawah ini - dan yang satu tidak boleh ada di sana:
sama ketika saya menggunakan skrip ini:
EXEC distribution.dbo.sp_replmonitorhelppublication @publisher='my publisher'
Pertama, Anda melakukan apa yang ditunjukkan dalam jawaban lain di atas, jika itu berhasil , itu baik-baik saja, kadang-kadang berfungsi, masalah dipecahkan.
itu akan lebih dari itu:
exec master.dbo.sp_replicationdboption @dbname = 'my_PUBLICATION', @optname = N'publish', @value = N'false'
exec master.dbo.sp_replicationdboption @dbname = 'my_PUBLICATION', @optname = N'publish', @value = N'true'
sp_droppublication @publication='my_PUBLICATION'
-- Remove replication objects from a subscription database (if necessary).
exec master.dbo.sp_removedbreplication 'my_PUBLICATION'
exec master.dbo.sp_removedbreplication 'my_PUBLICATION'
use my_PUBLICATION
sp_removedbreplication @type='both'
USE [master]
EXEC sp_replicationdboption
@dbname = N'my_PUBLICATION',
@optname = N'publish',
@value = N'false';
GO
EXEC distribution.dbo.sp_replmonitorhelppublication @publisher='PUBLISHER_SERVER'
sp_replmonitorhelppublisher @publisher='PUBLISHER_SERVER'
DECLARE @publicationDB AS sysname;
DECLARE @publication AS sysname;
SET @publicationDB = N'my_PUBLICATION';
SET @publication = N'my_PUBLICATION';
-- Remove a transactional publication.
USE my_PUBLICATION
EXEC sp_droppublication @publication = @publication;
-- Remove replication objects from the database.
USE [master]
EXEC sp_replicationdboption
@dbname = @publicationDB,
@optname = N'publish',
@value = N'false';
GO
Sekarang untuk menyingkirkan sepenuhnya publikasi ini kita akan mulai dengan koneksi ke buscriber, dan kemudian penerbit, dan kemudian distributor sesuai skrip di bawah ini:
-- Connect Subscriber
:connect [SUBSCRIBER_SERVER]
use [master]
exec sp_helpreplicationdboption @dbname = N'SUBSCRIBER_DATABASE'
go
use [SUBSCRIBER_DATABASE]
exec sp_subscription_cleanup @publisher = N'PUBLISHER_SERVER', @publisher_db = N'my_PUBLICATION_DB',
@publication = N'my_PUBLICATION'
go
-- Connect Publisher Server
:connect [PUBLISHER_SERVER]
-- Drop Subscription
use [my_PUBLICATION]
exec sp_dropsubscription @publication = N'my_PUBLICATION', @subscriber = N'all',
@destination_db = N'SUBSCRIBER_DATABASE', @article = N'all'
go
-- Drop publication
exec sp_droppublication @publication = N'my_PUBLICATION'
-- Disable replication db option
exec sp_replicationdboption @dbname = N'my_PUBLICATION_db', @optname = N'publish', @value = N'false'
GO
-- Connect Distributor
:CONNECT [PUBLISHER_SERVER]
go
exec Distribution.dbo.sp_MSremove_published_jobs @server = 'PUBLISHER_SERVER',
@database = N'my_PUBLICATION'
go
--===========================================================================================
--THAT DOES NOT GENERALLY GET RID OF THE JOBS FOR YOU
-- so you need to find them using these selects, and get rid of them manually yourself:
--select * from Distribution.dbo.MSpublications
--select * from Distribution.dbo.MSpublications
--===========================================================================================
select * from Distribution.[dbo].[MSlogreader_agents]
where publisher_db = N'my_PUBLICATION'
--found 1 job:
--PUBLISHER_SERVER-my_PUBLICATION-11
--script the job
--script the job delete script - and run that - keeping the job creation script just in case
exec msdb.dbo.sp_help_job @job_id=0x93C63D34E357704B818312B93FCA02FB
exec msdb.dbo.sp_delete_job @job_id=0x93C63D34E357704B818312B93FCA02FB
select * from Distribution.[dbo].[MSdistribution_agents]
where publisher_db = N'my_PUBLICATION'
--here found 2 jobs:
--PUBLISHER_SERVER-my_PUBLICATION-my_PUBLICATION--67
--PUBLISHER_SERVER-my_PUBLICATION-my_PUBLICATION--68
--here is the problem - it cannot find the jobs, the jobs are not even there anymore, one of those things
exec msdb.dbo.sp_delete_job @job_id=0x0F1564BAACD5464C988DE8957C25C411
exec msdb.dbo.sp_delete_job @job_id=0x6215C40F999CE248A30EE735E2C0E59D
--Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers, Line 41 [Batch Start Line 52]
--The specified @job_id ('BA64150F-D5AC-4C46-988D-E8957C25C411') does not exist.
--Msg 14262, Level 16, State 1, Procedure sp_verify_job_identifiers, Line 41 [Batch Start Line 53]
--The specified @job_id ('0FC41562-9C99-48E2-A30E-E735E2C0E59D') does not exist.
exec msdb.dbo.sp_delete_job @job_name='PUBLISHER_SERVER-my_PUBLICATION-my_PUBLICATION'
PUBLISHER_SERVER-my_PUBLICATION-my_PUBLICATION--68
pada titik ini buat kembali publikasi seperti biasa
lalu pasang snapshot untuk dijalankan
tunggu sampai selesai membuat snapshot
MAYBE YOU DONT NEED TO RUN THE SNAP
- coba without
jalankan dulu, sebagian besar waktu tidak berfungsi, Anda juga dapat menambahkan hanya 1-2 small
artikel ke publikasi sehingga snap berjalan cepat
tetapi jika Anda menjalankan snapshot maka Anda harus menunggu sampai selesai sebelum Anda dapat melanjutkan ke langkah berikutnya - drop the publication
setelah itu Anda menghasilkan skrip drop that publication
sesuai gambar di bawah ini:
semoga setelah itu, ketika Anda menjalankan skrip asli kami di atas , atau melihat monitor replikasi Anda tidak akan melihat publikasi yang salah, hanya yang baik, dalam kasus saya hanya satu: