Sharepoint bug when deactivating features
I have found that deactivating a feature in Sharepoint leaves erroneous entries in the AllDocs table in the content database. These table records then make deploying other features that contain the same filenames impossible as Sharepoint complains that they already exist. How can I make sure deactivating features does not leave old references in the content database?

Microsoft explicitly says that we should not execute queries directly on the database otherwise it will become unsupported.

all the best
Sharepoint bug when deactivating features
===

I have found that deactivating a feature in Sharepoint leaves erroneous entries in the AllDocs table in the content database. These table records then make deploying other features that contain the same filenames impossible as Sharepoint complains that they already exist. How can I make sure deactivating features does not leave old references in the content database?

Microsoft explicitly says that we should not execute queries directly on the database otherwise it will become unsupported.

all the best