Date Question

crisg0112

Hi,

When you use a Date Attribute in AwareIM, the internal storage on MSSQL is a smalldatetime. Why not just set it to a datetime and don't worry about any limits? The range of a smalldatetime is January 1, 1900 through to June 6, 2079 while a date time is January 1, 1753 - December 31, 9999

I have this issue trying to import the data from a legacy system, 10+ years ago and somehow, the user have 'misstyped' the date ( don't ask how :p ).

Has anyone come across a migration issue like this and what is the best way to fix this?
a) Get them to fix it??
b) Don't upload old data??

4xjbh

I am relatively new to aware,

Will using a timestamp instead of date solve your problem?

If you are sure not all of the data is valid it may be worth importing the dates from the legacy system to a plain text attribute and then do a check on the data with aware rules / processes. Doing it this way will mean you will have the original values at hand to keep checking the validity of each error the 'developer' created by allowing the date to be saved incorrectly.

Some other things to think off:

Some will also say not to import data into you main BO's. I am not sure about this, I just use an "Imported' flag and a CreatedAt attribute to track when it was imported.
Always make your attribute length longer that you think, you dont want to truncate any original data if you can help it. This may be another case for #1

EDIT:

Always work out a way to check for duplicates from different combinations of attributes. This may be another case for #1

crisg0112

4xjbh wrote
I am relatively new to aware,

Will using a timestamp instead of date solve your problem?

If you are sure not all of the data is valid it may be worth importing the dates from the legacy system to a plain text attribute and then do a check on the data with aware rules / processes. Doing it this way will mean you will have the original values at hand to keep checking the validity of each error the 'developer' created by allowing the date to be saved incorrectly.

Some other things to think off:

Some will also say not to import data into you main BO's. I am not sure about this, I just use an "Imported' flag and a CreatedAt attribute to track when it was imported.

Always make your attribute length longer that you think, you dont want to truncate any original data if you can help it. This may be another case for #1

Thanks, will keep that in mind.

crisg0112

Just as a follow up, on MSSQL, it doesn't matter if you use Date or Timestamp attribute, it gets stored as 'smalldatetime'.

Support, any chance that if its a Timestamp, to use datetime internal storage?