microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets
Issue with different time zones between environments
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 494
- Forks
- 296
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 5
Description
File /Analytics/DataverseLink/EDL_To_SynapseLinkDV_DBSetup/Step1_EDL_To_SynapseLinkDV_CreateUpdate_SetupScript.sql is using getdate() for declaration of the newdatetimemarker which can cause an issue by transferring data between environments with different time zones.
My example is: Synapse link uses UTC time, but destination server was set up with Paris/Berlin... time zone.
I mean this piece of code:
declare @newdatetimemarker datetime2 = getdate();
I would use getutcdate() instead.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open Analytics/DataverseLink/EDL_To_SynapseLinkDV_DBSetup/Step1_EDL_To_SynapseLinkDV_CreateUpdate_SetupScript.sql and inspect the newdatetimemarker declaration. Confirm the setup script uses a UTC-based timestamp so transfers between environments with different time zones use the same time reference; no test file is mentioned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100