Synchronization Synchronization is useful to get a local object copy from database to memory and vice versa. It also helps ...

|
Synchronization
 Synchronization is useful to get a local object copy from database to memory and vice versa. It also helps to find the differences between a local copy and the original database.
This tab allows changing the behavior of synchronization with database functionality. Several actions can be performed while the synchronization process is running. They are available in the Object Change Statuses list box:
 
  
Workspace copy of object has been changed, but database copy has not - An object loaded in the workspace from the database was changed (for example, its SQL was modified), but in the database it was not changed.
  
Database copy of object has been changed, but workspace copy has not - An object loaded in the workspace from the database was not changed, but it was changed in the database (for example, it was removed from the database by third-party software).
  
Both copies of object have been changed - An object loaded in the workspace from the database was changed (for example, its SQL was modified), and it was also changed in the database (for example, it was removed from database by third-party software).
  
Database copy of object exists, but workspace copy does not exist - A connection by SSMA to the database was performed before the object was added to the database.
 
 
With all change statuses described above, the following actions can be associated:
 
  
Do nothing - The system will do nothing.
  
Always overwrite database object with local copy - The system will overwrite the database object with the copy contained in the workspace.
  
Always overwrite local copy with the database object - The system will overwrite the local object in the workspace with the object contained in database.
  
Ask user - A dialog will ask the user what to do.
 
 
When the object is being synchronized with the database, its SQL code is being run against the database. When synchronizing a group of objects, it is possible that the script will fail because it refers to another object from the list that is not loaded yet. In this case, the script needs to be run one or more times. The parameter Maximum number of attempts controls how many times synchronization will be attempted in case of error.
|