Once the database is populated, you will have enough information to modify
the few hard-coded procedures.
Place holders for all hardcoded values are bracketed (i.e. '[place holder]')
verify_dump and verify_load - These procedures use a remote procedure call
and returns an OUTPUT value. That's a difficult combination for dynamic SQL. Both procedures
first check to see if the server where the information is requested
is the local server. If it is not, the procedure call
needs to be prefixed with the correct remote server's name to access that server. Modify (and add if necessary)
an entry for each server added to the servers table. You'll need to modify the procedure to hold hard-coded values
for each server under the subsystem's control.
set_to_hot_site - This procedure sets database options for all databases on a hot spare server.
In the event that any user database(s) on the server should not be set with the hot site options
(for example test, development, static, and highly transient data stores), add
the name of the database to the conditional statement that will exclude such databases.
This procedure will work as is if you have no user databases you wish to exclude from the hot site database
options settings applied.
get_password - This procedure is a dynamic lookup device that will keep you from having to
save the password to each server in your environment in clear text in systasks. Run the get_password_template
procedure and follow the instructions to create your initial version of this procedure. Once the initial
version is created, the add_server and remove_server procedures will properly maintain the get_password
Some of the products that appear on this site are from companies from which QuinStreet receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. QuinStreet does not include all companies or all types of products available in the marketplace.