IMPORTANT!  When deleting a logical reader it will also purge all the logging that has occurred (under that logical reader) based on the the physical readers that are currently assigned (or have been assigned in the past). This can take a considerable amount of time as all the reader logging activity will be deleted before disassociating each physical reader profile. To speed this up refer to this section on associating a binding profile to a physical reader profile that will delete the logging via high speed SQL.

Note: Even if you were to disassociate the physical readers first, then delete the logical reader, it will still take the same amount of time as it will go through the logging database looking for any records with that logical reader.

IMPORTANT!!  When deleting a logical reader it will also delete all the physical readers that are assigned to it, this can be dangerous if you have assigned production readers to a test logical reader group. Additionally, this can take a considerable amount of time as all the reader logging activity will be deleted before removing each physical reader profile.

A best practice is to disassociate the physical readers first, then delete the logical reader profile. At that point you can delete the physical readers individually if that is required. Refer to this section on associating a binding profile to a physical reader profile that will delete the logging via SQL (prior to deleting the physical reader profile itself).

Delete Logical Tag Reader

Deletes the profile as shown if [Yes] selected