Open DavidKDeutsch opened 8 years ago
I see, that's why!. Just downloaded from releases and saw it was a bit outdated, but tried anyway, and failed.
Will build and try, thanks mate.
confirmed this is still an issue.
@martincheck Sql2016+ has built in timezone support. https://docs.microsoft.com/en-us/sql/t-sql/queries/at-time-zone-transact-sql?view=sql-server-2017
@martincheck Sql2016+ has built in timezone support. https://docs.microsoft.com/en-us/sql/t-sql/queries/at-time-zone-transact-sql?view=sql-server-2017
But unfortunately Microsoft has its own ideas when it comes to naming time zones. I had been using the built-in, but just found this gem of a project and am pretty sure this is the best solution (until the legacy code that is hitting my DB can be updated to do this itself and not rely on the DB.
The latest release of SqlTzLoader.exe at https://github.com/mj1856/SqlServerTimeZoneSupport/releases looks for the DB connection string in a config file, whereas the instructions at https://github.com/mj1856/SqlServerTimeZoneSupport indicate you should use the command line to specify the connection string. Looks like the latest source does support the command line method, so I'll build from that.