Forum Replies Created

Viewing 15 posts - 121 through 135 (of 186 total)

  • RE: How to tune/speed up a procedure

    By golly, does this look correct?

    UpdateIARTS..PWDPermitConversionData2

    Set

    ConversionStatusPrev1 = Case When (Select 1 From PermitsInserted p2 Where p2.PWDPermitConversionDataID = p.PWDPermitConversionDataID And p2.RecordIndicator = 1) = 1 Then 1 Else Null End,

    ConversionStatusPrev2 =...

  • RE: How to tune/speed up a procedure

    lmu92 (4/16/2010)


    gregory.anderson (4/16/2010)


    It might be required to catch the [PWDPermitConversionDataID] values and the column that failed for the rows holding bad values (using the OUTPUT clause applied to the error...

  • RE: How to tune/speed up a procedure

    It might be required to catch the [PWDPermitConversionDataID] values and the column that failed for the rows holding bad values (using the OUTPUT clause applied to the error checking statement...

  • RE: How to tune/speed up a procedure

    I've been racking my brain on the very last step of this "previous" permit section...with just a yes or no, is it even possible to update the ConversionStatusPrevX fields with...

  • RE: How to tune/speed up a procedure

    It's simply bad coding habit together with lazyness anda good portion of luck...

    The reason why the code doesn't fail is that there are no duplicate column names used. So, to...

  • RE: How to tune/speed up a procedure

    That example of the cross apply stuff makes it look so easy. Once the article mentioned it was just like a method in programming, it kind of clicked for me.

    If...

  • RE: How to tune/speed up a procedure

    Oh, by the way, I let my old version run and finish while I/we've been working on the new set-based solution...the only version finished in 11 hours, plus 18 hours,...

  • RE: How to tune/speed up a procedure

    I wasn't sure if the columns I used would make the rows unique... Obviously, they didn't.

    Well, you were closing to making it unique. The combination of PermitNumber and PWDPermitTypeID would...

  • RE: How to tune/speed up a procedure

    The update of the conversionstatus statement isn't working how I want because it updates ALL of the records even though only 557000 of the 680000 are getting inserted (because of...

  • RE: How to tune/speed up a procedure

    Again, WOW!

    When I got to work this morning, MY version was still running and SSMS said the run time was at 18 hours, and that started at half-way through the...

  • RE: How to tune/speed up a procedure

    Thanks WayneS for the links...pretty straight-forward once I know what they do...

    I just created duplicate PWDPermit, PWDPermitConversionData, and PWDPermitConversionErrors tables so that I could compare the results. Just ran the...

  • RE: How to tune/speed up a procedure

    Side-tracked by production issues right now, I'll let you guys know when I get back to this....

  • RE: How to tune/speed up a procedure

    lmu92 (4/14/2010)


    Ok,

    here's part 1. It should cover everything except the handling of (@PermitType = 'M')

    I expect you have a test environment so you can verify if it will return the...

  • RE: How to tune/speed up a procedure

    lmu92 (4/14/2010)


    gregory.anderson (4/14/2010)


    Let's see how this works:

    bad sample data

    Don't remember how much I pasted before, but this is everything up until the first "Select Top 1" statement

    Well, this way of...

  • RE: How to tune/speed up a procedure

    Data type mismatch: [PermitNo] [int] vs. [PermitNumber] [varchar](6)

    I did this because the previous conversion to get to the mainframe/VSAM version caused some bad data to be created. There are records...

Viewing 15 posts - 121 through 135 (of 186 total)