Groups | Blog | Home
all groups > sql server replication > october 2006 >

sql server replication : Replication Active Connection


Hilary Cotter
10/20/2006 11:01:56 AM
If the third party software needs access to the subscriber database you
could stop the distribution agent, or have the third party application put
the database in read only or single user mode before it starts to do its
work.

--
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



[quoted text, click to view]

masmith via SQLMonster.com
10/20/2006 2:52:44 PM
Using SQL Server 2000 transactional replication which is running continously
to populate our reporting server. We have a thrid party software which we
need to use a interface to take a cvs file and import it into their database.
The interface requires that it has exclusive access to the database. Since we
are running replication there is always a constant connection to the
published database. Is there away to stop that connection. I have tried
stopping the synchronization but it seems to me the only way to remove that
connection is to delete the publiction. Is there an easier way.

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-replication/200610/1
AddThis Social Bookmark Button