>>>>>I have bulk records that are getting imported into a SQL Server 2005 table. I need to be able to maintain the same order that they were imported. I was using a DateTime field and populating it to GETDATE(), but that wasn't precise enough.
>>>>>
>>>>>Any advice out there?
>>>>
>>>>In SQL Server 2005 there is no date types with high precision. There are several in SQL Server 2008 (DateTime2).
>>>
>>>Any other ideas? I received a recommendation elsewhere to rely on the autoincrementing identity column, but I've always believed that to be bad practice.
>>
>>Check last suggestion from this thread http://social.msdn.microsoft.com/Forums/en/transactsql/thread/3db0d9c8-7fe5-4adf-80df-7ee76da891c2
>
>Ah, very very interesting. I'm open to trying that, but I've never done anything like that before. I'll have to do some research.

The interesting thing is that I'm listening right now Kendra Little session about date types.

http://www.sqlpass.org/24hours/spring2011/SessionsbySchedule.aspx

See attached.