The replication process begins with subscription materialization, which is the process by which data is first copied to the destination database. When you no longer want a subscription replicated to a destination database, you dematerialize the subscription at the destination database. Dematerialization is the process by which data is deleted from the destination database. Subscription failures occur when materialization or dematerialization fails.
Usually, the person who is conducting the materialization or dematerialization monitors the operation and reports any problems.
Subscription problem symptoms are easily identified and include:
Materialization failure – no data in the subscription’s replicate table at the destination database, the status for subscriptions at the primary and replicate Replication Servers is not Valid, or materialization has been taking longer than is reasonable.
Dematerialization failure – data still exists in the subscription’s replicate table at the destination database, the status for subscriptions at the primary and replicate Replication Servers is not Invalid, or dematerialization has been taking longer than is reasonable.
Some subscription problem symptoms are displayed as error messages in the Replication Server error log. You might also need to use the diagnostic tools to identify subscription problem symptoms. For more information about subscription problems, see “Troubleshooting subscription failures”.
