Replication and DBCCs

I want to run dbccs against replicated databases, dbcc_checkdb etc. Does
replication need stopped in order to facilitate the dbccs'? Should a new
snapshot be taken following the dbccs?
No need to reinitialize, pause etc - you can run these in place.
If yo are running DBCC DBREINDEX you might notice some delay before the
synchronization completes though because of the locking issues.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Thanks Paul.
"Paul Ibison" wrote:

> No need to reinitialize, pause etc - you can run these in place.
> If yo are running DBCC DBREINDEX you might notice some delay before the
> synchronization completes though because of the locking issues.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||There have been some reports that some DBCC commands make the log reader
stop reading transactions. This was in SQL 2000.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"DC_SQL_GUY" <DC_SQL_GUY@.discussions.microsoft.com> wrote in message
news:8947CD19-95C7-45F8-9403-92DF293F731E@.microsoft.com...
>I want to run dbccs against replicated databases, dbcc_checkdb etc. Does
> replication need stopped in order to facilitate the dbccs'? Should a new
> snapshot be taken following the dbccs?
|||We experience similar things during our weekly DBCC REINDEXing on the
replicated database. It stops the distributor from applying replicated
transactions and causes the distribution agent to timeout and fail eventually
after the retry count is exceeded.
Is there a way to automate the checking of distribution agent if it is
running at the end of REINDEXing and to restart distribution agent if not.
Thanks
PVG
"Hilary Cotter" wrote:

> There have been some reports that some DBCC commands make the log reader
> stop reading transactions. This was in SQL 2000.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "DC_SQL_GUY" <DC_SQL_GUY@.discussions.microsoft.com> wrote in message
> news:8947CD19-95C7-45F8-9403-92DF293F731E@.microsoft.com...
>
>
|||You could modify the reindex job to have an additional step before :
exec msdb..sp_stop_job 'distribution agent job name'
and an additional step at the end:
exec msdb..sp_start_job 'distribution agent job name'
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||How about scheduling the distribution agent not to run in the interval you
are doing your re-indexing.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"PVG" <PVG@.discussions.microsoft.com> wrote in message
news:199ED0FD-FEE5-47AA-BE0D-CD08BB4C5B92@.microsoft.com...[vbcol=seagreen]
> We experience similar things during our weekly DBCC REINDEXing on the
> replicated database. It stops the distributor from applying replicated
> transactions and causes the distribution agent to timeout and fail
> eventually
> after the retry count is exceeded.
> Is there a way to automate the checking of distribution agent if it is
> running at the end of REINDEXing and to restart distribution agent if not.
> Thanks
> PVG
> "Hilary Cotter" wrote: