Just put a default of getDate() on those columns.  No need to have an insert trigger then.  YOu'll simply need an afeter insert for the midified by and date columns.

Why...

It takes 2.5X times (IIRC) while it resorts the data, it basically makes a copy of the table in tempdb while working this out.  Then it also has to write...

Also implied with this  >>> run off hours if at all possible!!!!!

Well not only would it take time but it would require 250% of the space the table occupies now (while doing the work).  So I would withdraw this solution in...

That one I can confirm... It's per physical socket.  Even a quad core should cost only one license (I guess it could change on there end however).

No, only an update command can do that .  You can transform the data as you wish when you select it

I can't answer the first one (but I think standard), but I'm sure you have to pay only for 4 (physical) processors.

How does this work for you?

SELECT CONVERT(VARCHAR(10), GETDATE(), 101) AS MMDDYYYY

OR

SELECT CONVERT(VARCHAR(10), DateCol, 101) AS DateCol from dbo.YourTable

Cool, we'll call that the first test for red-gate !

Thanx for the info... will make the necessary modification to the maintenance plan!.

ok and for ultra small databases (250 MB >> 10 users)?

Ok thanx... 2 databases : single application.

FREEPROCCACHE it is.

How often would you suggest running the update stats / reindex commands?

Just to clarify that.  Asking for help 3 message in a row is how I felt like we had to serve you.  I'm happy to hear that this is not...

BTW you have a trailing space in count of unique claims that you have in the where that you don't  have in the sort.... that sure can't help!

SELECT CalcAction FROM...

So basically after reindexing (not updating the stats) the whole db you need to clear the proccache??