Microsoft SQL Server 7.0 Storage Procedure Debug Guide Summary: Describe how to use Microsoft Visual InterDev's SQL debugger to clear the error during Microsoft SQL Server storage.
Using Visual InterDev Clears the Forms in the Storage Process and Trigger If you are using Microsoft Visual Studio Enterprise Edition, Visual InterDev contains a SQL debugger. You can use it like processing other scripts or programs, clear the errors in the SQL Server storage process and flip-flops. However, some differences on how to set SQL debugging and how the debugger is executed.
Setting SQL debugging for SQL settings:
You must have a Visual Studio Enterprise. You must perform SQL Server 6.5 containing Server Pack 2 or later. We recommend using version 7.0. SQL Server must be executed on a version of Microsoft Windows NT 4.0 or higher. Your workstation must perform Windows 95, Windows 98, Windows NT 4.0 or later. To use SQL debugging, you must make an appropriate settings for the server and workstation. You should:
Determine the SQL debug assembly has been installed in SQL Server. Create a Windows NT user with administrative privileges on the SQL Server computer. Set the Distributed Component Object Model (DCOM) on the server for SQL debugging. Determine the client's DCOM setting support SQL debugging (only for Windows 95, 98 workstations). Installing the SQL Server Debug Component SQL Debug Requirements You need to install the components of your SQL Server. These components are part of the Visual Studio Enterprise version.
Installing the SQL Debug Components On the computer where SQL Server is installed, launch the Visual Studio Enterprise Edition setup program. The installation wizard displays different options based on whether or not to install the server components on your computer. If the server is already installed, select the server application and tool in the new / delete option. If there is no other component, select Next until the page that provides the enterprise setting option is reached. Select server applications and tools. If you do not install other components, choose the next step until the page that provides the enterprise setting option is reached. Select server applications and tools. In the next page, select Start BackOffice Installation Wizard and select Install. When the BackOffice Business Program Wizard is displayed, select Custom Install and select Next. Continue to press Next until you see a page that provides a list of installation components. In addition to the following components, remove the remaining components: SQL server debugging. MS data access components. Visual InterDev server. Press Installation. Set a debug user To use SQL debug, you must provide an account and password for Windows NT users with administrative privileges on the computer that performs SQL Server.
Set a user for SQL debugging to use in the Windows console in the server, select Set a debug user, then select the service. Select MSSQL and select Start. The selected login account is the set value. If this option is set to the system account, change it to this account, and enter the correct domain and user account of the user with administrative privileges in the form of the domain / account. If this set value has changed, restart the SQL server. Set DCOM for SQL debugging Use If possible, keep a local copy in the machine, then you can do not need to use DCOM to perform cross-engine debugging.
SQL debug uses a Distributed Component Object Model (DCOM) to communicate between your client computer and database servers. Therefore, DCOM must be set to allow remote users to attach a handler on the debugger.
By default, the correct DCOM setting value is set when installing SQL Server on the server. However, for the safety of the SQL Server computer, you may have to limit access to debugging. To set DCOM on the server for SQL debugging with the Windows Start menu from the server, select Run, and then type DCMCNFG.EXE in the prompt of the box. In the Distributed Component Object Model (Distributed COM) Set the content window, select the preset security page. Select the editing preset under the preset access rights. If you have no permissions, choose Add, then add a domain and user account with a user who has administrative privileges as a domain / account. After adding this account, check SYSTEM. If it has not yet appeared on the list, add a list of selected add names and group dialogs. If you have modified any options described in this process, restart SQL Server. Note: If you want to add your account to the remote server, this account cannot perform debugging, the user who may be the account is being executed on the server computer.
Execute SQL debugging and clears the error of other kinds of programs, you cannot clear the storage process or to the trigger program being executed. You can open this procedure in your editor and clear errors there.
In the Data Check window, press the right button on the storage process and select Debug.
The editor opens the storage process in its window and then selects the debug command in the debug menu.
After opening the editor window in debug mode, you can use the debugger pointer as usual. For example, you can set a breakpoint and progressively executed a process in this window. You can view the value of the variable. You can also drag the expression to the Watch window to use it step by step or execute the program. The results of SQL Print are displayed in the output window.
However, the debugger used by the SQL debugger and scripts has the following differences: Auto and Immediate window are no effect on the storage process debugging. Although you can display them, the Auto window will become empty, and the Immediate window will not allow you to enter an expression. You can change the execution order to specify the next statement using the settings.
If you are using a simple SELECT statement - those only return a single value - the number of returned values is a variable that can be viewed in the native window. However, if the SELECT statement passes back a result set, it will not be displayed in the debugger. In addition, you can view the result set on the output window.
