Link an NDB to the Project

The NDB contains the recipients information which are referenced in the templates of the project. You need to link this specific NDB to the right project, otherwise the notifications will be sent to the wrong recipients. To avoid a mismatch, the NDB and the project get the same key.
If a mismatch is detected, you are informed with a pop up message. In that case, you need to link the NDB to the right project. If there is no matching NDB available, then you need to delete all the recipients in the project, create a new NDB, create the recipients in the project again and link the recipients to the template.
The following steps illustrates the workflow:

  1. In the SMC tree, select your project.
  1. Select the Notification tab.
  1. In the SQL Server Details expander, select the NDB from the Linked NDB drop-down list.
  1. Click Save.
  • The NDB is linked with the project and logs history data.

If you move with SMC the NDB for example, from a local SQL Server to a remote SQL Server, that at the time of move execution (unlink from old, link to new NDB) both NDBs must be reachable. The reason behind this behavior is a so called consistency key which binds a CC project to a NDB to make sure, that the CC project is always connected to the right NDB, with the right recipients. If a new NDB is needed, then the consistency key will be red from the old NDB and moved to the the new NDB.