My application is standalone windows application. Database is SQL Server 2008 onward. The application will be deployed on systems around the globe. User should view the date/time values in their own culture.
There are some Date, Time and DateTime columns in database. Should I store them:
- based on SQL Server Date/Time?
- based on Windows Date/Time?
- based on Windows Date/Time converted to UTC?
I think I do not need to look into this globalization part at all as the application is standalone and databases are never going to be shared. Data will stay at same machine only, it will not be moved to central location. So, second option is best suited I guess.
I read this question and its answer.
DateTimeOffset looks odd; it is generally used for row versioning. I am not sure if it is needed here. That answer is not even accepted; not sure if it really helped OP.