![]() The cookie is used to store the user consent for the cookies in the category "Analytics".cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. These cookies ensure basic functionalities and security features of the website, anonymously.ĬookieDurationDescriptioncookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. Necessary cookies are absolutely essential for the website to function properly. But opting out of some of these cookies may affect your browsing experience. You also have the option to opt-out of these cookies. These cookies will be stored in your browser only with your consent. We also use third-party cookies that help us analyze and understand how you use this website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. ![]() This website uses cookies to improve your experience while you navigate through the website. However, you may visit "Cookie Settings" to provide a controlled consent.Cookie SettingsAccept AllManage consent By clicking “Accept All”, you consent to the use of ALL the cookies. We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. We realize smart software solutions to make managing and changing IT environments easier and cheaper. Save my name, email, and website in this browser for the next time I comment. Your email address will not be published. This risk can be mitigated with proper testing. In order to make sure that this setting doesn’t have destructive effects, I strongly recommend to store the timezone that was used in the session. There is a risk that a timezone is set on session level. An ELT-tool should be used for production loads.The workaround I recommend is to set the timezone explicitly in the session where data is loaded. In case the timezone changes due to new insights, the ACCOUNTADMIN needs to be aware of that changing the timezone can cause new TS_LTZ timestamps to get corrupted. ![]() The Snowflake ACCOUNTADMIN has the rights to change the timezone on the production Snowflake account.Therefore, there is no risk that corrupted LTZ timestamps are loaded. However, they should not be privileged to load data into snowflake tables. A Snowflake-developer can change the sessions timezone.There are three scenario’s that I can think of that can cause this to happen. The only way that LTZ Timestamps can get corrupted is when the session timezone accidentally overwrites the account timezone.Corrupted LTZ Timestamps only impact the production account.I agree with Randy that this risk exists, but at the same time I would assess its probability to be low:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |