0
0
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 – 2012-11-27T10:44:49.570
Timescales, It could and should be done but I've never written a C# service and the deadline approaches like the grim reaper..... – Paddy Carroll – 2012-11-27T10:54:48.770