I still want Brian to tell us what the EXE does and how many rows per call it's going to handle.

I'm thinking in the SQL side but could probably also be done on the ASP side.  In either case (sorry about the pun), financial calculations should probably not have general...

Yep... you're correct... require a particular format.  I recommend TAB delimited files so that quotes and commas can be included as part of the data, if the customer desires.

And, I'm...

How'z that work Peter... sounds interesting but also sounds like it might be a cursor and I'm thinking I know you better than that...

[EDIT] Oh...

What does the EXE do?

Macro that executes on load and reexecutes every 10 seconds should do it

Dinendra,

First, don't even think cursor... especially not for this size table...

The following is fully programmable...

You need to use some CASE statements, at the very least.  Accounting functions are way too important to trust defaults.

Even if the perfect indexes were present, it's not likely they'd be used because of the calculations on columns in the WHERE clause... there's even a UDF in there...

"Hopefully this...

You might also want ot learn how to use OSO-11179 naming rules

Yep... especially when it comes to...

No such thing in SQL Server 2000.  You can make one with a trigger on each table and a "LastModified" table... just be careful not to make any deadlocks...

Some hard disk systems (SAN's, etc) come with clone and snapshot systems that will do this in scant minutes for a half-terabyte database.

There isn't one in T-SQL. 

Um... not sure... but I think you may have missed the point...

What does the "executable" actually do?  And for how many rows per call does it do it?

Eamon,

Drop the target table (takes indexes with it) and do a SELECT collist INTO tgttable FROM srctable WITH (NOLOCK).  Then, reapply your indexes.  If it takes more than 10 minutes...