I have a job that needs to go off every minute or so,

it loads a DLL i have written in C# that retrieves state for an SQL Server Mirror (Primary, Mirror and witness) for a number of databases;

it allows us to poke DNS to show where the primary instances are. Please don't mention Clustering - We're not doing that.

I can't be arsed to write a service, there simply isn't enough time

do I

  • Task Scheduler - every minute: Invoke a powershell script that loads the DLL does the business
  • Task scheduler - At Startup : Invoke a similer powershell script that loads the DLL once but then loops and sleeps, refreshing the Object that the DLL exposes.

Pros and cons?

  • If you can't be 'arsed' then why should we be 'arsed' to help?
    – Dave
    Nov 27 '12 at 10:44
  • Timescales, It could and should be done but I've never written a C# service and the deadline approaches like the grim reaper..... Nov 27 '12 at 10:54

Powershell is a heavy thing to load every minute for a small task. You can create mass swap in this way. From this point of view the second approach looks a little bit better. But in the second case monitoring this job if it is running or not will be your problem.

So, if you have enough cache memory to fit powershell with its dependencies - try the first option. If not - stick with the second. And think of writing service anyway :)

  • I shall write the service - but not this week. Thanks! Nov 27 '12 at 16:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.