Re: Starting Snapshot Agent causes the DB machine to hang
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Wed, 22 Aug 2007 15:28:25 -0400
Can you use the concurrent snapshot option? This will prevent the massive
locking which can occur when your snapshot it being generated.
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
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
"Wasyl" <Wasyl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:274FD4E0-4F0D-4D47-B60D-A177BA7895B7@xxxxxxxxxxxxxxxx
Hi,
When I try to start the snapshot agent for a transactional publication it
is
hanging my database machine and makes it totally non-responsive until I
have
to switch it off manually. Just now this happened and I restarted the
machine, tried to start the agent again and it became non-responsive about
1
minute later.
This particular publication I have in the past initialised on this server
in
the exact same setup and had no problems, it just seems to happen about
70%
of the time. The machine is a HP DL380, 2 Dual core processors, 4GB ram,
Windows 2003 Server and MSSQL 2005 SP2 Standard Edition.
I have a staging server setup with exactly the same versions of Windows
and
MSSQL but a lower spec machine. This machine I can re-initialise the
same
subscription on a backup of the production database and it has never
failed.
Also on the machine that hangs, if I have a console logged in with task
manager running, when the machine hangs and all the SQL transactions stop,
the task manager still ticks away showing no spikes in memory or CPU. In
fact the CPU basically stops doing anything. I have waited 1.5 hours in
one
case and had no change. As soon as I try to click on anything inside this
console it becomes non-responsive and the task manager graphs stop
updating.
I have tried reformatting the drive, re-installing SQL Server and still
the
same thing happens. The machine is not showing any hardware problems, the
event logs are empty and the SQL server logs contain nothing useful. Does
anyone have any ideas?
Some extra info:-
The publication is about 1.6GB in size
The subscriber is running over a VPN over the internet (although the
subscriber does not have to br created for this to hang)
The snapshot seems to start fine and run for a small amount of time then
hang half way through a bulk snapshot copy
I have several other publications running on that machine, the next
biggest
.
- Prev by Date: Re: Could not find stored procedure
- Next by Date: Re: Distribution db for Bidirectional Transactional Replication
- Previous by thread: Distribution db for Bidirectional Transactional Replication
- Next by thread: Re: Starting Snapshot Agent causes the DB machine to hang
- Index(es):
Relevant Pages
|
Loading
