>I think you should consider using default values in the table DDL.
>
>For instance...
>
>

>create table test  (firstname varchar(10), lastupdatetime datetime2 default sysdatetime() )
>

>
>Most DBAs would agree these should be set in the database, not in the application layer.
>
>(And I just noticed that Mike Yearwood replied the same way....and Mike is correct 99.9999999999% of the time) :)

All the values are controlled by the application. If VB.NET does not currently support that type by the use of the SQLClient, I will have to wait before its usage. But, I would assume this is probably already supported by now. I just need to find some times to get into that by next week.

I had this situation today that I inserted a bunch of records with the same millisecond. As I order a list using by most recent, it appeared not exactly in the order I expected. This was a first of course. So, this is why, whereas applicable, I would focus on enhancing in that direction.