Now my website is on windows azure. I make a store procedure in database, then I execute it to update database every night on 0:00:00. I use azure automation to achieve this goal. So I write a Runbook which execute this store procedure. And add a scheduler to this task. Now this all work well, but in the scheduler, I set the time "0:00:00" which can't set the time zone.
(I am in China, but this task always run before 0:00:00 compared to my local time)
How can I specify the time zone when setting a scheduler on azure automation?
As you may already know that everything in Azure runs in UTC. If you want to run your task at midnight China time, what you could do is calculate the time difference (which I believe is 8:00 hours) and run your task at that time which would be at 4:00 PM UTC ( assuming my math is right).
Related
I am having several Copy activities in Azure Data Factory Pipeline from Azure SQL Source to Azure Data Lake Store for different tables independent of each other.
I have scheduled it for every 15 mins. I am seeing a time lag of around 1 minute while triggering such as 12:00 AM jobs are triggering at 12:01 AM.
Also only 2 copy activities getting kick started at a time out of 20+ activities remaining getting triggered one by one .
Is this expected behavior? Any ways to eradicate this time lag?
According to SLA for Data Factory, Activity Runs SLA is within 4 minutes. And also a common practice is to avoid o'clock spike, especially for 12AM (UTC).
I have created a web application in which I'm using sails.js framework and mongodb for back-end purpose. I want to implement a cron job running at midnight of each day so that I can calculate previous day's power consumption of a property. This data has to be used for reporting purpose.
The cron job has to run w.r.t properties location, i.e, if 2 properties are located at different time zones, I have to run the job when midnight occurs for each time zone.
I am using IIS-8 under Windows Server 2012 R2. and the time for both the IIS & windows server were exactly the same. but this week we changed our server time be adding one hour for daylight saving time. this caused our IIS time to be different than the real time.
now I am using a schedule tool named hangfire which execute background jobs and it is hosted under IIS, and I am allowing users to determine the schedule time using a UI.
The problem is that currently if we set the schedule time for example to be 18:00 , it will be executed at 19:00. also the IIS logs time is one hour pass the actual time. so can anyone advice on this please?how i can force the IIS time and date to be in-sync with our windows server time and date?
Thanks
Do you have IIS applications running under a service account? Try logging in with the service account creds and check the regional settings for that account.
Currently from the Azure portal (old portal) when setting up a scheduled job start time, you can only specify times as half hour intervals like 12:00 or 3:30 but you can't tell it to start from say 12:55. Is there another way to set up a scheduled job that allows for any start time?
You can either use the new portal, which enables you more advanced options along side with the ability to set the scheduling to a minute granularity. Or use the REST api to do a request with a specific time/interval.
Hope this helps!
Mert
I have a timer clocking every one minute in C# window Service. And, This pc is running 24 hours and never shut down. My workflow is that user will set the time for my service to run some processes. eg. he set 14:20. So, When my timer hit 14:20, I run some sql functions. Will it be any impact on performance If i run the timer like that for 24 hours?
Is there any better way?
You could use something like Quartz.NET: http://quartznet.sourceforge.net/