I just voted for "plz send answer". 🙂

Strong hint: a poll is not really useful to ask a question. You should start a thread in the related forum section.

The chance...

If it's an option I would recommend to move to 2K8 instead of 2K5.

Keep in mind that mainstream support for 2K5 will end in less then a month (4/12/2011).

Maybe this link[/url] will provide the information you need.

tuseau (3/16/2011)

---

...

So, the reason I can't perform DDL statements or use truncate is because the application is being designed for concurrent transactions. Truncate will interfere, and obviously so...

You don't have to post any actual data. Either make something up or use AdventureWorks tables that would describe your scenario. Once you have some sample data you should post...

How many rows do you have in that table? And how many rows per Symbol (approximately)?

Reason for asking: This code performs a triangular join that might seriously influence performance...

UPDATE

DWH_THE_ALLIANCE

SET

DWH_THE_ALLIANCE.SOLUTIONTYPE_LLAV_PR = 168

FROM DWH_THE_ALLIANCE t1

INNER JOIN DWH_TDI_SOLUTIONTYPE tsol ON t1.SOLUTIONTYPE_LLAV_PR = tsol.SOLUTIONTYPE_LLAV_PR

INNER JOIN DWH_TDI_OPPORTUNITY topp ON t1.OPPORTUNITY_LLAV_PR = topp.OPPORTUNITY_LLAV_PR

WHERE

topp.Status = 'WIN' AND

t1.TIME_LLAV_PR >= 20100701 AND

t1.SEBL_ID IN (

'CRMAP1-6-1DUXOPH'

) AND

t1.SOLUTIONTYPE_LLAV_PR = 155;

What's wrong with my answer?

I think you need the additional column to store the intermediate running toal values. To calculate those values, have a look at this post.

LutzM (3/14/2011)

---

jason-772533 (3/14/2011)

---

I checked the 'Forums' list before I posted and couldn't see a 2K forum. I've just checked again and there isn't one listed. There is an 'Older versions'...

jason-772533 (3/14/2011)

---

I checked the 'Forums' list before I posted and couldn't see a 2K forum. I've just checked again and there isn't one listed. There is an 'Older versions' forum...

If you run a LIKE '%something' statement against a table you'll end up with a table/index scan.

One option would be to add an indexed computed persisted column with REVERSE(ID). Then...

The concept still applies:

DECLARE @temp TABLE

(

Description_ CHAR(1),

Category VARCHAR(30)

)

INSERT INTO @temp

SELECT 'A','apple' UNION ALL

SELECT 'A','aardvark' UNION ALL

SELECT 'A','anteater' UNION ALL

SELECT...

Please have a look at the CrossTab article referenced in my signature.

You might also continue with the DynamicCrossTab concept if you need even more flexibility.

donato1026 (3/11/2011)

---

...

Sorry, but I won't be able to do that. This can be used on any database . . . it's just the case statement I am having an issue...