|
About Replacing Objects
Many different aspects can effect the outcome no matter whether the process of replacing objects directly on a SQL server is straight forward. For instance, there is no error checking phase done on the objects before they are replaced which can cause the SQL server to throw an unexpected error when this process is done programmatically.
We must consider carefully before replacing objects. For example, if a trigger object is manually created in the system tables, there is no checking done to confirm if the parent table of the object exists. Then SQL Decryptor will fail to replace the trigger object on the server.
Important Notice
It is recommended that using a backup or copy of a database but not live or production database when you replace objects on a SQL server. We are not responsible in any way for any direct or indirect damages that may occur due to the use of this tool.
| 
