>>>>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.
>
>Why bad practice?
>
>I use identity columns for almost (like 98%) every SQL table I design. Works great and takes the guesswork out.

Yeah, must have read that somewhere and got it in my head it was a bad practice. It seems like it would work well in this situation.