If only there was some code, imagine what we could do to help.

--Dave

Double check your tempdb files count and make sure you have one tempdb file for every logical CPU in the machine even if you put additional tempdb files on the...

What data mining method are you trying to run for the model? Try upping your settings for minimum number of cases or/and probability percentage. The advanced setting have a huge...

Check hyper-threading and the number of tempDB files you have.

You may want to check that hyper-threading is turned off for your machine. Hyper-threading slows performance on SQL Server.

Also, you want...

Using Profiler should only add an additional 2% to your performance overhead. Check out the MSDN Webcast, Part 9 on Server-side Trace Queues. Also adding too many event/data columns...

LINQ in all its versions is (IMHO) nothing more than the Gentle.NET Framework which ceased development in 2006 http://sourceforge.net/projects/gopf with a few improvements.

I would continue to use stored...

Mitch,

No such luck out of the box for 2000. The autoindex solution relies on the system dynamic managment views which were new additions to 2005.

However, in theory you could...

If you have an ETL database for staging the data you would not have indexes on tables. The point of the ETL is to pull the information out and prep...

In a nutshell what I think you are looking at is the difference in 1M seperate insert/ update statements vs a batch transaction of one insert/update statement that contains 1M...

There are two compeating methodologies in the DW area and have been for a while. Kimbell with the Data Warehouse Lifecycle Toolkit and Inmon with the Corporate Information factory.

We covered...

Dan,

I have inherited many Access upgrades myself and found that they also have no keys and no indexes and performance was almost never good. I wanted to point you to...

My advice would be to listen to Paul in the above posting. He knows better then anyone else on here considering he was one of the principle architechtes and developers...

Be aware that you can get duplicate data back in a query using NOLOCK.

Itzik Ben Gan demoed this and you can find a code example here.

http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/11/16/1345.aspx

--Dave

Having been in the same boat many times before I know how to improve poorly written and designed application databases with a min. of effort.

So the first thing you should...

I was in the same boat recently and here is the best that I can point you to.

Take a look at Makeing Sense of Your Web Feedback using SQL Server...