Forum Replies Created

Viewing 15 posts - 136 through 150 (of 186 total)

  • RE: How to tune/speed up a procedure

    gregory.anderson (4/14/2010)


    PaulB-TheOneAndOnly (4/14/2010)


    gregory.anderson (4/14/2010)


    Ok, I modified the stored proc to add the @Today = GetDate() right before it does each insert into PWDPermit so I could gather some real timings,...

  • RE: How to tune/speed up a procedure

    lmu92 (4/14/2010)


    At a first glance it looks like it's not required to do it row by row...

    Beside the sample data I already asked for please provide the beginning of the...

  • RE: How to tune/speed up a procedure

    PaulB-TheOneAndOnly (4/14/2010)


    gregory.anderson (4/14/2010)


    Ok, I modified the stored proc to add the @Today = GetDate() right before it does each insert into PWDPermit so I could gather some real timings, right...

  • RE: How to tune/speed up a procedure

    Ok, I modified the stored proc to add the @Today = GetDate() right before it does each insert into PWDPermit so I could gather some real timings, right now, (still...

  • RE: How to tune/speed up a procedure

    I just added the unique index on the primary key, and unless I was way off on my previous tests, this appears to be around 5 times as fast...

    Edit: Ok,...

  • RE: How to tune/speed up a procedure

    PaulB-TheOneAndOnly (4/14/2010)


    gregory.anderson (4/14/2010)


    Thanks, I'll try that.

    Please let us know how it goes.

    Initial test, without gathering actual statistics, it's about half as fast. The actual execution plan shows the load on...

  • RE: How to tune/speed up a procedure

    Thanks, I'll try that.

  • RE: How to tune/speed up a procedure

    PaulB-TheOneAndOnly (4/14/2010)


    gregory.anderson (4/14/2010)


    After trying Elliot's suggesting about displaying the actual execution plan, it appears as though the most time consuming/resource intensive portions of the proc are in "Clustered Index Update"...

  • RE: How to tune/speed up a procedure

    Ok, I'll try and post the sql stuff...this is going to be long

    Staging Table

    CREATE TABLE [dbo].[PWDPermitConversionData](

    [PWDPermitConversionDataID] [int] IDENTITY(1,1) NOT NULL,

    [PermitPrefix] [varchar](1) NOT NULL,

    [PermitNumber] [varchar](6) NOT NULL,

    [CustomerNumber] [int] NULL,

    [SSN] [varchar](9) NOT...

  • RE: How to tune/speed up a procedure

    lmu92 (4/14/2010)


    gregory.anderson (4/14/2010)


    ...I am processing this where I do a Select Top 1 blah Where (criteria here) and assign the values in my select statement to variables. ...

    Is it possible...

  • RE: How to tune/speed up a procedure

    gregory.anderson (4/14/2010)


    After trying Elliot's suggesting about displaying the actual execution plan, it appears as though the most time consuming/resource intensive portions of the proc are in "Clustered Index Update" statements.

    By...

  • RE: How to tune/speed up a procedure

    The conversion from the mainframe data (in a VSAM file) inserted into the SQL staging table only takes a few minutes. Then I add some indexes to my staging table,...

  • RE: Dynamic SQL Statement - Problem with Syntax

    I got it. If @ErrorMessage was null, it would never build the dynamic sql...it would just set it to null also.

  • RE: Dynamic SQL Statement - Problem with Syntax

    Also, when I output the @ErrorMessage variable, it comes out as a space also.

  • RE: Row locking and Table locking

    GilaMonster (1/19/2010)


    Scans of the clustered index are table scans. They either indicate that a nonclustered index was not selective enough to be used, or there are nonclustered indexes missing.

    How did...

Viewing 15 posts - 136 through 150 (of 186 total)