I turned on profiler on my helpdesk database. I have a quick incident that takes 10-20 seconds to execute. This quick incident sets the Contact and Asset for the ticket. It appears by setting Contact and Asset, calls are made to 2 stored procedures.



sp_getcontactbyid

and

sp_getassetbyid





These procedures are taking the bulk of the time. Looking at them, it appears they limit the results against asset and contact views to 2000 rows. I'm guessing this has to do with the helpdesk interface and preventing too many rows from returning. Example, viewing a contact or asset and up to 2000 tickets associated with that contact or asset.





I'm willing to limit the results to say 100 rows instead of 2000. Can anyone see any harm from limiting the results to 100 instead of 2000 rows for these two stored procedures? Or, has anyone actually done this?