• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 8. Stored Procedures > Searching for Errors in Stored Procedures

Searching for Errors in Stored Procedures

Errors in stored procedures can lead to unforeseeable consequences in SQL Server and Access. Depending on the type and the gravity of the error, SQL Server will either continue or cancel execution of the stored procedure without informing Access what happened in SQL Server. Unfortunately, SQL Server often reacts to errors by terminating the corresponding database process, which can cause Access to freeze. Removing frozen database processes is described in Chapter 19, “SQL Server Tools,” in the section entitled “Processes and Locks,” and Chapter 23, “The SQL-DMO Library,” in the section entitled “Processing Information.”

The lack of support for Access 2000, Access 2002, and Microsoft SQL Server 7 when debugging stored procedures is extremely inconvenient. There is no option, for example, to run through a stored procedure step-by-step or to check the status and content of variables, and so forth. Only Microsoft SQL Server 2000 (but not MSDE 2000) provides more help in this area: The SQL Server program Microsoft Query Analyzer 2000, introduced in Chapter 19, “SQL Server Tools,” allows you do to debug stored procedures.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint