September 11, 2007 at 7:34 am
We have written a service application to take over the
automated processes that we used to use SQLServer Agent for. {SQL2005Express is being installed and has no Agent}
However, we've run into problems getting this to run external
programs reliably. We are attempting to run these processes in
the LOCALSYSTEM account and sometimes they just don't run at
all. If we set them to run in the Administrator account,
sometimes they don't run, either. It is really kind of a puzzle
that, on some systems, it runs in one but not the other and
vice versa.
Our question is, what security context does Agent run external
processes? If our service is multi-threaded, could that be a
cause of this behavior? What else could we look for to help us
figure this one out?
September 12, 2007 at 9:41 am
Let me see if I am on the same page ... You have written a service application that duplicates, for all intents and purposes, the SQL Agent. If I am on the same page I must ask ...
Why ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
September 12, 2007 at 10:03 am
I agree but please do without the typical IT-"everyone is stupid" attitude.
smv929
September 12, 2007 at 3:51 pm
Well, I forgot to mention that we are installing SQL2005Express on our client's systems.
DID YOU EVER THINK OF THAT?
I was asking about the security context for Agent, do you have any idea?
September 17, 2007 at 3:39 pm
Anyone else have anything to say here?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply