August 13, 2002 at 12:48 pm
I have posted this on several boards and not even as much as a peep. Let's see how you guys can do...
I have a primary server setup as a distributor and a publisher. It has two publications, one real-time merge, the other real-time transactional.
The secondary server has a subscription to each of the publications.
On the primary server, I show active connections from itself (host name is the primary server name) as the user distributor_admin. They don't consume much resources, but they begin to proliferate. After SQL startup, there is one connection. Within 1 hour, there are four. Two hours later now there ar 5. Prior to this last reboot, the server had been up for about 4 days and there were 49 distributor_admin connections.
Any thoughts?
Brian Glass
Sr. Database Adminstrator
Bombardier Aerospace
August 13, 2002 at 5:53 pm
What version of SQL and what service pack? Running the distribution agent continuously?
Andy
August 14, 2002 at 7:12 am
quote:
What version of SQL and what service pack? Running the distribution agent continuously?Andy
http://www.sqlservercentral.com/columnists/awarren/
SQL 7 SP 2 (upgrading to SQL 2000 SP 2 in 10 days). The distribution agent (run from the subscriber) is continuous. Both subscriptions are immediate updating.
Brian Glass
Sr. Database Adminstrator
Bombardier Aerospace
August 14, 2002 at 7:21 am
quote:
What version of SQL and what service pack? Running the distribution agent continuously?Andy
http://www.sqlservercentral.com/columnists/awarren/
Also, stopping and restarting the SQL Agent on either machine does not free up the connections. Only stopping the SQL Server service on the distributor/publisher clears them.
Brian Glass
Sr. Database Adminstrator
Bombardier Aerospace
August 14, 2002 at 10:48 am
Pretty strange. One thing you might try is killing them from task manager. One theory is that you're getting some kind of error that you're not seeing since it runs from SQL Agent. I'd start by turning on the verbose logging and see what that gives you. Might also want to try running distrib.exe directly so you can watch what it does - it'll open a console window.
Andy
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply