The Stored Procedure Search allows you to search for strings in database objects. Perhaps you need to know if any stored procedures or triggers update a certain database table column. This is the easiest tool around to do that.
At the top of the window is a field where you can enter the search string. The input field maintains a history of your searches and auto-completes as you type.
Next to it is a dropdown listing all the current object owners. You can optionally limit searches to a particular owner.
The center of the window is the result list. The type, owner and name are displayed. For all database types except ASA, it also shows create datetime.
Below the result list is the source code view. The string you are looking for is selected to make it easy to see. There is a horizontal sizebar in-between the result list and the source code view. You can slide it up and down to adjust how much you can see.
Actions:
Sort Data (Alt+S): Opens the Specify Sort window.
Copy (Ctrl+C): Copies to clipboard selected text from the source code view if it has focus, otherwise the object name.
Search: Starts the search process. Same as the Search button.
Prior hit (Alt+P): Skips to the prior hit in the result list and source code view.
Next hit (Alt+N): Skips to the next hit in the result list and source code view.
DB Profile: Opens the Database Profile window.
Edit Source: Edit the object source in the external editor.
Config ODBC: Opens the operating system's ODBC configuration tool.
Import Profiles: Opens the Import Database Profiles window.
Clear History: Clears the search field's dropdown history.
Databases:
The stored procedure search works with the following databases:
Sybase Adaptive Server Enterprise
Sybase Adaptive Server Anywhere (SQL Anywhere)
Microsoft SQL Server
Oracle
Types:
In Sybase ASE databases it searches procedures, triggers, view definitions, table names and column names.
In Microsoft SQL Server databases it searches procedures, triggers, view definitions and table names.
In Sybase ASA databases it searches procedures, triggers and view definitions.
In Oracle databases it searches procedures, functions, packages, package bodies, types and type bodies. It can't search triggers because they are stored in a different manner than other database objects. It also searches all object names.