When viewing the creation SQL for an object using the candidate list or any of the features that insert SQL e.g. the insertion of the object definition after an ALTER statement. SQL Prompt will use the version of the SQL code in its cache file and not retrieve that latest version from the database.

This means that you will see the SQL code from the last time the cache was updated and not what is currently on the server. If you are using the auto insertion of object definition after the ALTER statement and you haven't updated your cache after somebody has changed a stored procedure, it is possible to accidentally overwrite the new version of the stored procedure with the old version stored in the cache file.

Cause

SQL Prompt is using the version of SQL code in its cache file.

How to fix

Update the cache if you know that someone might have modified the procedure. You may update the cache using the cache management option from the SQL Prompt menu.

If you continue to experience problems, please contact Redgate Support.