Viewing 15 posts - 1,516 through 1,530 (of 5,502 total)
GilaMonster (5/23/2011)
May 23, 2011 at 2:41 pm
sgambale (5/23/2011)
Most queries need this refresh table, so that's the main problem and why a delete/insert is needed vs. truncate/insert.
There...
May 23, 2011 at 2:04 pm
sgambale (5/23/2011)
May 23, 2011 at 12:55 pm
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,...
May 23, 2011 at 10:36 am
laddu4700 (5/22/2011)
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...
May 23, 2011 at 10:20 am
GilaMonster (5/22/2011)
http://www.google.com/search?q=computed+persisted+columnIn most cases a computed column can be indexed without needing to persist it.
The reason for suggesting the column as being persisted was mainly driven by the (assumed) improved...
May 23, 2011 at 10:17 am
Something like this?
SELECT DATEADD(yy,-2,DATEADD(qq,DATEDIFF(qq,0,GETDATE())+1,0))
May 22, 2011 at 5:33 pm
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...
May 22, 2011 at 5:26 pm
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...
May 22, 2011 at 4:19 pm
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...
May 22, 2011 at 3:55 pm
I would probably use a calendar table and a second table to describe the shift pattern.
May 22, 2011 at 10:45 am
Errrmm... Did you read the article I pointed you at?
We might have a slightly different definition of "ready to use"...
May 22, 2011 at 10:34 am
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',...
May 22, 2011 at 10:25 am
It might be more efficient to unpivot the data instead of comparing column by column.
You could either lookup UNPIVOT in BOL (BooksOnLine, the SQL Server help system, usually installed together...
May 22, 2011 at 10:06 am
It depends on the scenario.
There are cases where a table variable would be preferred over a temp table (e.g. to capture some values even after a rollback). Without knowing the...
May 22, 2011 at 9:59 am
Viewing 15 posts - 1,516 through 1,530 (of 5,502 total)