eastern | Simple Kubernetes Deployment | Continuous Deployment library

You'll want to convert those zone strings into actual Time.Zones, which can be done with justinmimbs' TimeZone library.

Then, you'll need to get the current time with something like Time.every, and convert it to local parts with Time.Extra.posixToParts.

Some example code:

var t = new Date() - not passing anything to the Date constructor will make it "right now". I think you need to pass the iterated date to the Date constructor:

The SQL Server import facilities are very intolerant of bad data and even just formatting variations or options. In my career, I have literally spent thousands of work-hours trying to develop and debug import procedures for customers. I can tell you right now, that trying to fix this with SQL alone is both difficult and time-consuming.

When you have this problem (bad data and/or inconsistent formatting) it is almost always easier to find or develop a more flexible tool to pre-process the data into the rigid standard that SQL expects. So I would say that if Excel can parse it then just use Excel automation to pre-process them and then use SQL to import the Excel output. If that's not practical for you, then I'd advise writing your own tool in some client language (C#, Vb, Java, Python, etc.) to pre-process the files.

You can do it in SQL (and I have done it many times), but I promise you that it is a long complicated trek.

SSIS has more flexible error-handling for problems like this, but if you are not already familiar and using it, it has a very steep learning curve and your first SSIS project is likely to be very time-consuming also.

Thanks to the discussion on my original question and per the understanding I gained from the blog post by Paul Ganssle, I replaced my timedelta.total_seconds() math with:

You need the -Stream switch to instruct Out-String to output individual lines - by default, you'll get a single, multi-line string.

Also, you can simplify your string-insertion task with the help of the -replace operator:

Yes, you can display the date however you like it. Read the Kendo Date Parsing documentation. I would suggest though that the back-end send it in ISO format (e.g. yyyy-MM-ddTHH:mm:ss). So that on the front-end, you can just do parseDate without the need for additional parameters. Perhaps depending on the language setting of the browser it will be shown in AEST or AEDT format. If not, then you can do toString on the date.

With case_when you could extend: (more conditions):

As you already know how to set the at command to execute a command at the specified time, and how to convert the EST to the local time, you can just combine them:

DateTime's fromISO takes string. I was comparing string with Date. That was the mistake. Solution is fromJSDate