Difference between revisions of "arsdoc update"

No change in size ,  11:56, 12 November 2020
m
Formatting tweak for CMOD arsdoc update article.
m (Formatting tweak for CMOD arsdoc update article.)
 
Line 55: Line 55:


== Changing the data with arsdoc update ==
== Changing the data with arsdoc update ==
[[File:Attention.png|70px|left]] WARNING:  There is no 'undo' command for <code>arsdoc update</code>.  The changes you're requesting are usually made in a fraction of a second, and there will be no way to revert the change back to the original state.  It is a wise and prudent move to create a full, offline database backup immediately before running <code>arsdoc update</code>, as well as exporting unmodified copies of your tables to revert changes with relative ease.  Contact your local DBA for assistance in creating backups of the OnDemand management tables (starting with 'ARS'), and Application Group tables that will be modifed, so they can be restored without requiring a database outage for a full restore.
[[File:Attention.png|50px|left]] WARNING:  There is no 'undo' command for <code>arsdoc update</code>.  The changes you're requesting are usually made in a fraction of a second, and there will be no way to revert the change back to the original state.  It is a wise and prudent move to create a full, offline database backup immediately before running <code>arsdoc update</code>, as well as exporting unmodified copies of your tables to revert changes with relative ease.  Contact your local DBA for assistance in creating backups of the OnDemand management tables (starting with 'ARS'), and Application Group tables that will be modifed, so they can be restored without requiring a database outage for a full restore.


Formulating the actual <code>arsdoc update</code> command is tricky, and takes practice to get right.  Your command should be tested on non-production OnDemand servers, and verified to be providing the correct results BEFORE executing them in a production environment.
Formulating the actual <code>arsdoc update</code> command is tricky, and takes practice to get right.  Your command should be tested on non-production OnDemand servers, and verified to be providing the correct results BEFORE executing them in a production environment.