Script the table with indexes and then delete the table, clustered index.

We don't have a matching thread view for the forums. We decided to go with a fixed level of forums.

If you want a tree view of articles, it's here: http://www.sqlservercentral.com/articles/articleList.asp?categoryid=100

Colin,

I think we all aspire to be that DBA

I'm sure that there are some strange tweaks in the benchmarks. All of the submissions are geared towards promoting their own platforms.

I'll say this from my experience, which is limited...

You can limit the total memory SQL Server will use. Out of curiosity, how much memory on the server and what's the SQL Setting.

Can you put the entire error message and the code you're using in the post? Looks like the subject got cut off.

If you're building the app, I'd write the calc into a stored proc and have the insert/update and the calc/update occur at the same time.

Are reports retrieving the values?...

How are you importing the data? Many methods allow you to not fail on 1 error. Or you can import into a staging table and then clean the data.

PKs...

Actually I like this. It tells me who not to go to for a job. Kind of recruiting Darwinism

It creates more administration and complicates disaster recovery, but it can help. However it's not necessarily a big performance boost:

http://blogs.msdn.com/psssql/archive/2007/02/21/sql-server-urban-legends-discussed.aspx

Search naming standards on this site and you'll find a few references as well for helping with that.

http://www.sqlservercentral.com/columnists/sjones/pushftp.asp

http://www.sqlservercentral.com/columnists/sjones/serverconsolidation.asp

there are good reasons to go either way. You use an interest statement and a small app to load the stream makes the most sense.

The best way I know of is to do this in batches. Delete xx records, backup the T-log, repeat. This way you can prevent the log from growing too much....