There are no limits. And, there are tools available to manage the creation/modification of stored procs...

>>Further, if you are going to employ best practices with respect to SQL Server Development, you will use Stored Procedures to Update, Insert, Delete, and Query Data. Stored Procedures provide the level of security and control that developers and DBA's need.
>
>Hi John,
>
>I haven't started learning T-SQL or best practices for SQL Server yet, so pardon the newbie question. Some of my apps involve entities with lots of columns per table. With RVs you can just edit the view and TABLEUPDATE it. If you implemented a SP instead for insert/update, would you need one parameter in the SP for each updateable field in the table, or is there some way to pass some serialized data? If the former, are there any limits to this (ie, number of parameters a SP supports) or other issues to be aware of?
>
>TIA,
>
>-- Randy