Thanks Boris. It was in fact datetime, not smalldatetime. I did find the problem though. The datetime was passed as character string to the stored procedure and then in a fix (to use the datetime from the server) that variable was reset using GETDATE(). We switched to a different variable name, declared it as datetime and then stored the datetime to it using getdate() and it now is precise. Bad coding was the cause.



>>Storing sql server data in a stored procedure setting datetime value by getdate() however, it doesn't seem to be storing seconds. Too many transactions within the same minute. Anyway to get a more precise datetime value in a stored procedure other than getdate()? We were passing the datetime from VFP but with many workstations the time could be wrong on each (that will change and the datetime will come from a server in the future) but for now, I need to store the current datetime (including seconds) to a variable in a stored procedure which then stores it to a record. When we look later at the data, all of the minutes are the same on many records so the order by clause on the datetime column is not precise enough.
>
>If you use smalldatetime, yes, that would be the result. Change field type to be datetime. This is not related to SQL Server you use (I think so, becuase I can't test it right now) but with the field type.