Showing posts with label exe. Show all posts
Showing posts with label exe. Show all posts

Tuesday, March 27, 2012

distrib.exe Many instances running

How many instances of distrib.exe should be running?

Yesterday I created multiple publications in SQL 2005. without counting, it looks like each publication has its own distrib.exe.... it this the way it is supposed to work?

Each instance it holding 8k of ram (not a problem right now) but I have many more publications to create...

Please let me know if this is the way SQL server works now?

Hi William,

I am guessing you were used to different behavior on SQL2000 where only one instance of distrib.exe is used to service multiple publications\subscriptions to the same subscriber database. The new behavior in SQL2005 is actually the result of a change in the default value of the 'independent_agent' publication property from 0 (false) to 1 (true). So, you can get the same behavior as SQL2000 by changing the 'independent_agent' property from 1 to 0 via sp_changepublication. I am also a bit curious to know why you are creating many publications. If your goal is to have finer granularity for subscription re-initialization, you can actually perform article level reinitialization using sp_reinitsubscription.

-Raymond

|||

Thanks for the explanation. I just wanted to make sure it was normal...

The reason for the multiple publications is not for the purpose of the subscriptions but rather the publications them selves. We have about 200 table that are changing several times a year based (data lenghts or additional columns). The table are bundles together based on when they are anticipated to change.

This is the explanation I was given when I was hired. I think it is just to make it easier to see what is what without opening the publications.

distrib.exe & logread.exe

Win & SQL 2K
What is distrib.exe? I have it running 15 times in my
task manager. It this a prog that distributes(pushes)
transactions to subscribers? Is this an SQL thing or
should I go look else where.
Also logread.exe is running 3 times. Is this anothere
SQL thing?
Larry...
Larry,
these are the 'engines' behind replication. When BOL talks about the
distribution agent, there is a SQL Agent job whose second step starts the
executable distrib.exe. For the logreader it is logread.exe. In
troubleshooting it is common practice to start the distrib.exe executable
from the commandline, especially when dealing with MSDE where there aren't
the graphical interfaces.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||thanks for the info Paul!!!

distrib.exe

Does the distrib.exe make a connection to SQL and read all the
trans/commands from the distrubution database to push to the subscribers ?
Yes! It reads from MSrepl_transactions and MSrepl_commands, although push or
pull obviously relates to where the agent is being run.
Rgds,
Paul Ibison
sql

Wednesday, March 21, 2012

Dissociation between DTS and Scheduled Job

Hi,

I've got a DTS package with a single step that runs an exe via Process Task. The DTS runs fine when I execute it manually, but when I schedule the package, the job says it runs successfully, but does not execute the package. Now, a few facts:

The DTS is owned by user1
The Job is owned by user1
All security credentials match up
The exe is on a network with full unc path specified
SQLAgent service is running in user1's context
All user input is on the actual SQL server, but exe is on network


When I change the DTS from running the exe to performing a simple query, the job executes the DTS just fine. When I move the exe from the network and place it locally on the server, the job still won't execute the DTS. What am I missing here? This is driving me crazy!!Shameless newbie bump...|||View the job history. Click the checkbox to show detail. Is there anything interesting there?

-PatP|||Hi Pat,

The job history tells me that all scheduled runs were successes, that the last step to run was step 1 (the only step), but the run time was one or two seconds. This one step that runs, however, should take between 2 and 3 minutes to complete (and does when DTS is executed manually).

That's all I get from the job history...

TIA|||SQLAgent service is running in user1's context
All user input is on the actual SQL server, but exe is on network

How is that possible?

In all my experience when a DTS package runs when manually executed, it's running under the context of the client, when scheduled, it runs under the context of the server...

Drive mappings and Security have always been the reason as to why the scheduled job fails...

Another reason why I stopped using DTS a long time agao for ANY production processes...