When the server| stored procedure first used SQL Server 2005, it did not know how to save it after modifying the stored procedure.
I found the appropriate stored procedure in the SQL Server Management Studio progammability, right click and select "Modify", will open the edit window, I modify and click Save, but the "Save File as" dialog box, Let me choose the saved path and filename, which is saved as another file instead of saving the modified stored procedure directly. I do not know why to design this way, I think the General people just start to use like me to operate. I also found no other way to operate in SQL Server Management Studio. That's depressing!
Later on the internet found an article "Saving Stored Procedure" to know how to save the modified stored procedures, it is by clicking the "Execute" button (or press the F5 key). I thought this operation was directly executing the stored procedure. I later discovered that when the edit window was opened through "Modify", the "ALTER" keyword was added before the stored procedure, so when the stored procedure was actually modified through the "execute" stored procedures, the SQL statements in the stored procedure were not executed. This reminds me of VS 2003 and VS 2005, when you edit a stored procedure by adding the "ALTER" keyword before the stored procedure, but in VS 2003 and VS 2005, clicking the Save button directly saves the changes to the stored procedure. I think the design in SQL Server Management Studio is not very reasonable.