I recommend going for ease of maintenance (IMHO).  Let Moore's Law take care
of performance. http://www.intel.com/intel/museum/25anniv/hof/moore.htm

-----Original Message-----
From: Arbon Reimer [mailto:arbon_reimer@h...]
Sent: Tuesday, May 29, 2001 11:01 AM
To: sql language
Subject: [sql_language] many little SPs or one big SP


Hello!

I have a bunch of updating/moving around to do in a billing database, 
and I had a question about performance.

Is it better to put it all in one big huge stored procedure or is it 
better to split it up into smaller stored procedures that do one task 
each?

My thoughts were that if I split it up into little tiny bits I could 
figure out more easily where the process blew up... If (when) that 
happens... but I wasn't sure about its affection of database 
performance.

If it makes any difference, I am calling these stored procedures from a 
COM component using ASP.

Thank you all in advance for your reply

Regards,
Arbon Reimer