Metadata Lock

If you want to alter a baseline metadata record, then you need to Lock the record by selecting the Metadata Lock flag on the form.

Doing so will prevent the netFORUM Deploy Tool from trying to update that particular record during an Upgrade.

It is not necessary to lock custom metadata that you add. The Upgrade Tool ignores metadata that has been added, it only cares about metadata you've altered where that same metadata is in our distribution database (which is the new version of the database what gets used for upgrades). In those cases, the Upgrade Tool will assume that the metadata in the distribution database is "right" and the same metadata record in the client database is "wrong", and the upgrade tool will update the client data to be identical to the distribution data unless the particular row is locked.

Uses

Jon Gilpin has created a new Stored Procedure md_metadata_lock_cleanup that is working well to remove the orphan records in the table md_metadata_lock. If anyone wants to use it for their database, please contact him.

This SP should be run with caution. There are times that we do the following:

1. Lock a baseline metadata row. This will insert a record in [md_metadata_lock]

2. Delete the baseline metadata row. This will leave an "orphan" row in [md_metadata_lock].

There is some value in #2 because baseline will never try to put that record back into the metadata table.

In reality, we should not be doing this, but with our earlier implementations we would sometimes lock a metadata, then delete it. This SP, when it deletes the orphans, will allow those metadata records to come back.