When you populate it use ORDER BY column ASC then store a boolean value with the datatable, e.g. bool isSortedAsc = true; Then, if you need to flip the order you will know which order it is currently in by the Boolean flag. ColinMackay.net Scottish Developers are looking for speakers for user group sessions over the next few months. Do you want to know more?

Hi Rania. Well, I think using a trigger is going to be your best bet for performance, over, say, additional C# code that would execute a separate command that the DB has to process anyway. Is your trigger doing other things besides the insert into your history table that would slow it down? Is the history table indexed? huge too? Is it possible the slowness is coming from having to refresh indexes on each insert to the history table?

You can use an SQL TRIGGER to create these records automatically whenever a modification is performed. (see CREATE TRIGGER in the SQL documentation). Also, you can use the COLUMNS_UPDATED() function to determine which columns have been changed (in order to produce the text for the column name). Hope this helps. Regards, Alex