Is there a particular reason to be using it or an easy way to override this behavior? MSDN doc is recommending using datetime2 over datetime, and we are currently facing an issue where because of this, the precision of the datetime is lowered and we are receiving incorrect results.
Is there a particular reason to be using it or an easy way to override this behavior? MSDN doc is recommending using datetime2 over datetime, and we are currently facing an issue where because of this, the precision of the datetime is lowered and we are receiving incorrect results.