GilaMonster (5/23/2011)

---

LutzM (5/23/2011)

---

Regarding the specific situation: it might be better for the person in question to officially ask for support. Try to deal with the situation "undercover" would just increase...

Based on some of your latest reply I might have to re-evaluate my position regarding NP organization... 😎

Regarding the specific situation: it might be better for the person in question...

GilaMonster (5/23/2011)

---

Just got a PM and a mail asking for some free consulting. I sympathise with people in tough situations, but that doesn't mean I'm willing to give telephonic support...

sgambale (5/23/2011)

---

There are 5 or 6 tables in the query plus aggregation.

Most queries need this refresh table, so that's the main problem and why a delete/insert is needed vs. truncate/insert.

There...

sgambale (5/23/2011)

---

I continually inform the users (there is one main user who runs these long queries) to break down the queries, but assume that some queries are just going to...

Straight from BOL:

Statements that make a simple assignment always set the @@ROWCOUNT value to 1. No rows are sent to the client. Examples of these statements are: SET @local_variable, RETURN,...

laddu4700 (5/22/2011)

---

Resolved.

parent table column referring itself. that is why my sp is getting error nesting level exceeded (limit 32).

I have modified SP and it worked

WHERE SO2.Name = @cTableName and so1.name...

The reason for suggesting the column as being persisted was mainly driven by the (assumed) improved...

Something like this?

SELECT DATEADD(yy,-2,DATEADD(qq,DATEDIFF(qq,0,GETDATE())+1,0))

I think the biggest issue is the clustered index scan of the cov table.

It might help to add a computed persisted column to get rid of the CASE expression on...

You could setup an audit table to identify how often a trigger is fired and how many rows are inserted/deleted.

But this would require to touch each and every trigger. If...

Please provide table def and index def for the tables involved.

At a first glance it looks like there's a missing index to support the t.rid = c.rid join (among others).

What...

I would probably use a calendar table and a second table to describe the shift pattern.

Errrmm... Did you read the article I pointed you at?

We might have a slightly different definition of "ready to use"...

Or, get rid of the c.u.r.s.o.r. and the dynamic SQL in the first place and use a set based solution:

DECLARE @tbl TABLE

(

organization VARCHAR(10),

data_viewVARCHAR(10),

subgroup VARCHAR(10),

amount INT

)

INSERT INTO @tbl

VALUES ('EAGLE','INTERCO','SMASGRP',...