Powershell, Task Scheduler or loop and sleep

Question

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?

Answer 1

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 :)