Editing Stored procedure (section)

== Disadvantages ==
* Stored procedure languages are often vendor-specific. Changing database vendors usually requires rewriting existing stored procedures.
* Changes to stored procedures are harder to keep track of within a version control system than other code. Changes must be reproduced as scripts to be stored in the project history to be included, and differences in procedures can be harder to merge and track correctly.
* Errors in stored procedures cannot be caught as part of a compilation or build step in an application IDE - the same is true if a stored procedure went missing or was accidentally deleted.
* Stored procedure languages from different vendors have different levels of sophistication.
*Tool support for writing and debugging stored procedures is often not as good as for other programming languages, but this differs between vendors and languages.
** For example, both PL/SQL and T-SQL have dedicated IDEs and debuggers. PL/PgSQL can be debugged from various IDEs.