LP_CUSTOMER_RANK

Gawain Lavers $organization over 10 years ago

We run a number of procedures out of LP_CUSTOMER_RANK, and I was just fixing one up. The SQL is much cleaner now, but this has come at the expense of speed: 6ms originally for one with a lot of structural information hard-coded into the procedure, now 100-200ms for one that derives the structural information from tables. Is there a good rule of thumb for how many milliseconds of execution you can get away with in this proc before you start to degrade performance of the client?

Thanks,

Gawain

Parents

Troy Nelson $organization over 9 years ago

Here, at the museum, we have these lines right after the comments

IF @customer_no is null
RETURN

-Set flag in connection context to allow certain table triggers to not update last_update_dt
EXEC AP_SET_CONTEXT 'LockTrigger', 'Y'

your code

At the bottom I see
Regards,
Troy Nelson
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- Cancel

Reply

Troy Nelson $organization over 9 years ago

Here, at the museum, we have these lines right after the comments

IF @customer_no is null
RETURN

-Set flag in connection context to allow certain table triggers to not update last_update_dt
EXEC AP_SET_CONTEXT 'LockTrigger', 'Y'

your code

At the bottom I see
Regards,
Troy Nelson
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- Cancel

Children

No Data