Thanks for the suggestions. That is direction I've been leaning. But that then leads to the question of what is the best method for copying out the data to another table without impacting the performance of the logging table? If I run a query hourly that copies over new data, something like...

INSERT INTO dbo.NewTable (LogID, LogMessage, DateStamp)

SELECT LogID, LogMessage, DateStamp

FROM dbo.OldTable

WHERE LogID > @MaxPreviouslyInsertedID

... without NOLOCK won't that query negatively impact the writes on the logging table?