Personally, I don't think my answer was any better than Steve's.  I think his answer was probably just as "correct" as mine.

But to address your concern about needing to add...

I agree with Steve here - why would you want to avoid the JOIN?  Put a good index on it and you should be good to go.

As an alternate approach...

My opinion - I think it really depends on what you need and what growth looks like.

I would personally put the data and log files on different disks if you...

With most SQL related things, I try to avoid the wizards.  I find that while they may work, it usually ends up making things in a way I don't want...

I agree with Grant here.  I find that MOST of the time when I think a Cursor is required, it is just that I have been doing too much .NET...

My understanding - even on a SAN the performance benefits may be lost.  The idea is to have it on separate physical disks.  once you start working with virtual disks,...

I agree with Joe on this one and would disagree with aaron.reese.  Parsing a string like that in SQL is going to be painful and adding more logic into the...

If you are getting the results you need, is there a reason to go with DISTINCT instead of GROUP BY?

If you absolutely need to remove the DISTINCT and replace it...

I can think of a few approaches, but my recommendation is to scrap that process and instead use stored procedures and have your code call the stored procedure instead.  This...

• This reply was modified 3 years, 10 months ago by Mr. Brian Gale. Reason: adding more info

What I am expecting is happening is that the datatype of BillingRateB is going to be something like VARCHAR and the value is something along the lines of '' or...

Might be a silly question, so feel free to ignore this, but do you really need the DATE and TIME in 2 different columns?  I have seen systems do this...

As a guess - I would say that the report is rendering and/or calculating out the number of pages it needs which is why you need to wait.  When the...

From looking at what you have, I think I see what is wrong.  You are inserting into AllData the columns, but since you are not specifying a column to insert...

Another way to optimize the sort operation would be to remove it by removing your ORDER BY statement.  If you don't order the data, no sorting would be required.

That is a painful problem to solve.  The other problem that can arise is how many columns do you need to make to handle current state and future state?

My opinion...