Lynn Pettis (4/27/2009)

---

greatheep (4/27/2009)

---

So, I have to agree with some of the thoughts I've seen on the board - namely, so far, the article(s) have not shown a case where...

Nice article. So what's considered excessive trigger use? We have some triggers that are 2000 lines and do a whole lot of data cleanup. They fire recursively too and we've...

Another way I've found to further increase performance when joining an indexed temp table is to run UPDATE STATISTICS on the temp table. I wouldn't think this would be necessary...

Jeremy,

I closed the window that ran the proc (spid 70) as well as the whole Management Studio app but the temp table was still there after refreshing the list of...

Matt,

Are you sure this is the case? I just created a proc which creates a temp table called "#temp" and ran the proc through SQL Management Studio. After the proc...

I agree with Jeff and bnordberg.

I see no reason to add a primary key/clustered index on this table as it appears to be an automatically generated IIS log file...

A few more suggestions:

-Temporarily disable any triggers on the table.

-Make DateInserted the first column in the where clause

-Create a composite index using DateInserted and Treated columns

-Update Statistics

What does the...

declare @IntVal integer

declare @HexVal varbinary(4)

set @IntVal = 212

select @HexVal = convert(varbinary(4), @IntVal)

select @HexVal

How about something like this:

DECLARE @varname Varchar(10)

SET ROWCOUNT 5000 -- Set this to however many rows you want to delete at a time

WHILE 1 = 1

BEGIN

DELETE...

Mel,

Given your hardware experience, have you seen substantial write performance differences when using difference drive interfaces, such as SCSI vs. Fiber Channel, SATA, etc...

Any recommendation for the best performance/cost ratio?

Erik

What about

update T2 set T2.Field1=T1.Field1,T2.Field2=T1.Field1 from Table2 T2 inner join Table1 T1 WITH (NOLOCK) on T2.Phone=T1.Phone

Maybe try some ROWLOCK hints depending on your needs.

Erik

Yes! That works.

INSERT INTO #temp

EXEC dbo.my_nested_sp @email = 'test@test.com'

Thank You!

 

I tried what you suggested but I still receive the additional result set from the nested stored procedure.

CREATE PROCEDURE dbo.my_main_sp

@email Varchar(80)

AS

SET NOCOUNT ON

DECLARE @rc Char(3), @Message Varchar(100),