This is a discussion on recompiling all affected procedure names within the Sybase forums, part of the Database Server Software category; --> Hello Wise People, I have a newbie question here using Sybase 12. I need to alter a stored proc ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello Wise People, I have a newbie question here using Sybase 12. I need to alter a stored proc on production. My boss says I should drop and recreate all stored procs that are dependent on this stored proc because of some bug that they saw where basically Sybase did not recognize a need to recompile affected procedures is there a command to issue in isql that will recompile? I know they have it in oracle. thanks for you wizardly advice Chris |
| |||
| I have not seen a need to recompile one stored procedure when another changes, unless the number or type of passed data items change. If a table structure changes or the data/statistics change significantly it is advisable to recompile each stored procedure that accesses that table. This is done by the sp_recompile <table name> . I routinely do this each time that I update statistics. |
| |||
| I have not seen a need to recompile one stored procedure when another changes, unless the number or type of passed data items change. If a table structure changes or the data/statistics change significantly it is advisable to recompile each stored procedure that accesses that table. This is done by the sp_recompile <table name> . I routinely do this each time that I update statistics. |
| |||
| Hi Chris! Just chiming in ... I agree with "wkra" (What's your name hon?) that there is no need to recompile dependent SP's unless they meet the criteria he specified ... Good luck in convincing your boss Chris! Cheers, Sara ... |
| |||
| In the sybase.public.ase.administration newsgroup, the "update statistics and sp_recompile " question was answered. Since 12.5.0.3 an update statistics will mark a table for recompile, eliminating the need to run sp_recompile. Will. |
| ||||
| hi all thanks for the replies it turns out on 12.0 whatever.. if you increase the tables size stored procedures on those tables that were altered need to be dropped and recreated because of an alignment problem that is not picked up with a recompile that is the answer that i got from them they ran into this bug and it was a nightmare hope this helps and if anyone knows more about it i'd be interested chris <wkraatz@csc.com> wrote in message news:1126533047.248472.175760@f14g2000cwb.googlegr oups.com... >I have not seen a need to recompile one stored procedure when another > changes, unless the number or type of passed data items change. > > If a table structure changes or the data/statistics change > significantly it is advisable to recompile each stored procedure that > accesses that table. This is done by the sp_recompile <table name> . > I routinely do this each time that I update statistics. > |