>>actually doing just fine except for the 1 SELECT SQL that is running much slower on SQL Server

Is this SELECT hitting 1 or more of the tables that are also...

Couple more comments/questions.

When you made the PKey nonclustered, did you make 1 of the alternate indexes clustered ? If not, that may actually worsen the situation and cause fragmentation. The...

There is a way to fix it, but it requires the business rules.

What does it *mean* to your business if there are 2 or more records in WorkExpense for the...

2 solutions:

1. Create a staging table. On every load, truncate the staging table, then perform the BULK INSERT to the staging table and not your permanent table.

Once data is in...

Some more questions then:

- Are there any triggers on the tables being inserted into ?

- Are there referential integrity constraints ? Are the tables containing the primary key side of these RI...

>>Hi, I don't know if there's a difference in the t-sql in 2005 and 2000

There is - the RANK OVER PARTITION is a T-SQL enhancement in 2005, which is...

Have you confirmed that the data and/or log files are not auto-growing ?

If there is a percentage based growth increment, it could explain the gradually worsening performance, as each increment...

Does the table being loaded to have many indexes ? Does it have a clustered index ? If it has a clustered index, does the data being inserted have a...

When you post a vague question, without providing any DDL for the tables, without providing any details on indexes, without providing any details on data volumes, then the advice of "why...

Try the 2 queries with SHOWPLAN turned on.

They'll probably resolve to exactly the same execution plan.

[Edit] If you're working in SQL2K5 Management Studio, paste the SQL into a query window, highlight...

Doh. You are correct of course.

Mental note to self: no forum postings before 1st coffee of the day.

>>but it does not aggregrate (sum) the rows

Do the columns being SUM()'ed allow NULL ? Summing a NULL value along with other values always returns NULL as the SUM() result.

Also,...

Go to the website for winzip and download the optional winzip command line.

The executable "wzunzip.exe" is the command-line unzipper that can be easily called from an exec process task.

Is the question about how to physically do the INSERT ?

Or is the question around how to schedule this ?

"It depends ..."

Updating 6mil records is not a specific enough description of the problem.

Width of records, number of data pages in the table ?

Type of application - OLTP with 24/7 availability...