Orhpan Records in MSP_WEB_ASSIGNMENTS - Valid?

B

Brent99Admin

Does anyone know if it is valid to have orphan records in the
MSP_WEB_ASSIGNMENTS table? In other words, when a project is deleted from
the system are the MSP_WEB_ASSIGNMENTS records supposed to be deleted or does
Microsoft leave them around for some reason?

I'm working with a client who has a lot of corrupt data from their old 2002
database which we recently upgraded. As part of the upgrade effort we wrote
some data integrity [orphan check] scripts and we have identified many
records in MSP_WEB_ASSIGNMENTS that no longer have a corresponding parent
record in the MSP_WEB_PROJECTS table.

For the life of me I cannot understand why this would be valid....based on
my relational database normalization and integrity knowledge. But if there
is a valid reason that someone knows of I would be very interested in hearing
from you.
 
G

Gary L. Chefetz \(MVP\)

Brent:

Keeping in mind that I can't make any statement for certain without seeing
the database and comparing before and after data states, it would be my
guess that the orphans were created before the plan was deleted. One would
think, however, that it would be easy enough for the deletion algorithm to
cleanup orphans as well, but then there's that inner thought nagging me that
the software shouldn't allow the creation of them to begin with. Such would
be the case if the join used in the delete statement linked assignments by
task ID only.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-
 
Top