SQL date/time import issue

Question

question

Sunil B2 asked Aug 18 2021 at 1:30 PM Sunil B2 answered Sep 01 2021 at 4:23 PM

SQL date/time import issue

When importing date/time data into global table from sql db , the data/time fraction is off by 420 years in fractions . Below picture shows the date, its value in excel and imported value via DB connection

see the attach model with copy paste and import. into global tables

Software Version:

FlexSim 21.1.5

flexsim 21.1.5 connectivity

1629292672737.png (4.8 KiB)

ms-sql-import-issue.fsm (27.7 KiB)

· 1

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2021-08-18T16:55:09Z

Ryan Clark answered Aug 18 2021 at 4:55 PM Ryan Clark commented Aug 19 2021 at 7:28 PM

Hello @Sunil B2,

It actually turns out that your SQL imported value corresponds to 420 years, 228 days, 8 hours, 29 minutes, and 50.237 seconds. This is the amount of time that has elapsed since January 1, 1601 12:00:00 AM, which is the earliest time/date currently allowed by FlexSim. My guess would be that FlexSim produces the time/date format by adding the EventTime in seconds to that initial value or something along those lines.

Does this address your question?

· 3

Sunil B2 commented · Aug 18 2021 at 11:33 PM

Ryan

No. Why did DB import offset by 420 years is the issue?

0 ·

Ryan Clark Sunil B2 commented · Aug 19 2021 at 7:28 PM

I'm attaching a model that just has a couple scripts in it. One of them converts a time into a date/time from Excel format, and the other in FlexSim format. But, they both output the same date.

Hope this helps!

SQL DateTime Convert.fsm

1 ·

sql-datetime-convert.fsm (25.0 KiB)

Ryan Clark Sunil B2 commented · Aug 19 2021 at 4:05 PM

I'm sorry for the misunderstanding. The difference between the Excel value and the SQL DB imported value is what date/time they are treating as zero and the units they are using to measure time.

Excel is using 12/30/1899 0:00:00 as its "zero-time" and is measuring the time since then in days.

FlexSim (and apparently the SQL DB, at least when imported) uses 1/1/1601 0:00:00 as its "zero-time" and measures the time since then in seconds.

I hope this helps!

0 ·

Answer 2 · 2021-09-01T16:23:41Z

Sunil B2 answered Sep 01 2021 at 4:23 PM

It seems to be a bug in Flexsim .. When I import into excel from MSSQL the date/time come correctly without any offset.

question