Deleting wrong record in t_seclocks

[wzr]

Hello,

when I'm transfering our DB from MSSQL-Server to a local eapx file i'm always getting an error message, saying that there is an entry in t_seclocks with an empty entity id. The transfer is still completing successfully, but the message annoying.

The result for the following query is exactly one row

Code: [Select]

SELECT *
from t_seclocks
where t_seclocks.EntityID = ''
Since this entry doesnt make any sense to me at all, I'm thinking of deleting this row by using the API:

Code: [Select]

Repository.Execute("DELETE from t_seclocks where t_seclocks.EntityID = '' ")
Do you see a chance that this will harm our model in any way?

[qwerty]

You should probably rather run a consitency check to do that for you.

q.

[wzr]

What consistency check do you mean and how to run it?

Configure -> Model -> Integrity -> Project Integrity doesn't report this point.

Thank you!

[wivel]

It seems to me that Consistensy Check does more behind the scenes, than what it reports, so you might be in luck, that the t_seclocks will be fixed anyway. I would try that out before deleting anything directly in the database.

That being said, Entity_ID should never be empty, so something is not right. If Consistency doesn't fix it, I would:
1. Backup the database using e.g. SQL Server Management Studio (its really fast)
2. Delete the t_seclocks row in error
3. Export again to an EAP(X) file

If something breaks, you can always roll back the database again.

Henrik
 

 

[qwerty]

Well, as he said. You could as well run a repository.exececute("DELETE FROM ....") to get rid of the records. Given you have the backup in any case...

q.

[Eve]

It seems to me that Consistensy Check does more behind the scenes, than what it reports

What gives you that belief?

The 'Report Only' action does not modify the database in any way.

The 'Recover/Clean' action only performs the 'Proposed Action' for each item from the report.

[wivel]

Hi Eve

Could that my not so reliable memory that is at play now. Years back on EA 6 or 7, i seem to recall we had an issue with not being able to Tagged Values on an element, that got fixed by doing a Consistency Check, even when the report said no errors.

It is a long time ago, so again, could be I'm wrong.

Henrik

[qwerty]

In any case the consistency check only puts out black smoke. None of the messages is really helpful to the user. There should be a log with details and possible explanations for the cause of the errors.

Just dreaming...

q.