Most likely you're trying to debug on a version of VS that doesn't support SQL debugging. You need Visual Studio Professional Edition or higher. Credentials used to run VS and to make connection to SQL Server must have SA role e.g. part of Administrators group on SQL Server box. Go to https://connect.microsoft.com/site/sitehome.aspx?SiteID=210&wa=wsignin1.0 and click on Submit Feedback and follow steps to file a bug/suggestion against VS debugger.

Unfortunately, the official specifications are not freely available (ANSI makes them available for purchase). However, there are books - such as SQL-99 Complete, Really by Peter Gulutzan and Trudy Pelzer - which give a comprehensive overview of the standard, including coverage of stored procedures.

In the proc table of the mysql system database. However, you should not access the tables in the system database directly. Instead, use SHOW CREATE FUNCTION to obtain information about stored functions, and SHOW CREATE PROCEDURE to obtain information about stored procedures. See Section 13.5.4.8, "SHOW CREATE PROCEDURE and SHOW CREATE FUNCTION Syntax", for more information about these statements. You can also query the ROUTINES table in the INFORMATION_SCHEMA database - see Section 22.

This is a privilege issue.You will probably get the error 1044 "Access denied ..." or 1370 "Alter routine command denied to user ...". ...

Yes. For a database named dbname, use this query on the INFORMATION_SCHEMA.ROUTINES table: SELECT ROUTINE_TYPE, ROUTINE_NAME FROM INFORMATION_SCHEMA.ROUTINES WHERE ROUTINE_SCHEMA='dbname'; The body of a stored routine can be viewed using SHOW CREATE FUNCTION (for a stored function) or SHOW CREATE PROCEDURE (for a stored procedure). See Section 13.5.4.8, "SHOW CREATE PROCEDURE and SHOW CREATE FUNCTION Syntax", for more information.

Yes. If a database schema has become inconsistent due to the use of sp_rename, and a stored procedure or a function definition refers to a different name from what is in the system tables, SQL Compare 6 automatically fixes these inconsistencies.

Not in MySQL 5.1. We intend to implement the SQL standard SIGNAL and RESIGNAL statements in a future MySQL release.

MySQL implements HANDLER definitions according to the SQL standard. See Section 18.2.8.2, "DECLARE Handlers", for details.

Yes, standard actions carried out in stored procedures and functions are replicated from a master MySQL server to a slave server. There are a few limitations that are described in detail in Section 18.4, "Binary Logging of Stored Routines and Triggers".

Yes, creation of stored procedures and functions carried out through normal DDL statements on a master server are replicated to a slave, so the objects will exist on both servers. ALTER and DROP statements for stored procedures and functions are also replicated.

MySQL records each DML event that occurs in a stored procedure and replicates those individual actions to a slave server. The actual calls made to execute stored procedures are not replicated. Stored functions that change data are logged as function invocations, not as the DML events that occur inside each function. Yes. Because a slave server has authority to execute any statement read from a master's binary log, special security constraints exist for using stored functions with replication.