P&ID Document settings

Hello Ken,

In order to avoid this issue in the future, I am attaching a SQL DB query that can be used to purge all of the database tables. USE THIS WITH CARE - it will purge every table.

I use this when configuring OpenPlant PID for a project. During the configuration phase, you will be adding components, modifying properties, adding new properties etc. In the process of testing your configuration, you will sync to the database. Over time, this fills the database with a significant amount of testing data. This data IS NOT needed for the actual project and can cause issues down the line.

When i am satisfied with the results of my configuration, I execute the query so that the project is starting clean. As i stated above - BE CAREFUL with the query, as it will purge data from all tables.

Other things to note:

1. If you add custom tables, these will need to be added to the query.
2. If you create a new Associated Item (Similar to PLANT_AREA), this table will also need to be added to the query.
3. You can remove some tables but be careful here too, as there are many links between tables and link tables as well. In the Plant Project Database documentation there is a ER diagram showing the relationships. This is helpful in determining what modifications will affect the various tables.

USE your database name here;

GO

DELETE FROM dbo.instr;

DELETE FROM DBO.EQUIP;

delete from TAG_REG;

delete from DOC_REG;

delete from KEY_LINK;

delete from EQP_LNK;

delete from INST_LNK;

delete from VALVE;

delete from VAL_LNK;

delete from OPPID_AREA;

delete from OPPID_UNIT;

delete from OPPID_SERVICE;

delete from OPPID_SYSTEM;

delete from OPPID_LINK;

delete from PROCESS;

delete from PIPE_RUN;

delete from RUN_CONN;

delete from PID_TOFR;

delete from PROC_LNK;

delete from NOZZLE;

delete from MOTOR;

delete from DEVICE;

delete from PID_TLNK;

delete from PID_LNK;

GO

I hope this helps,

Tony D said:

In order to avoid this issue in the future, I am attaching a SQL DB query that can be used to purge all of the database tables. USE THIS WITH CARE - it will purge every table.

Tony, thanks for the response.

My role here (Hatch) is as a Draftsman, not admin. I have a fair amount of knowledge about the database structure. However, I do not have access to the actual database. I will not run this routine, as it is not my role here, however I will talk to the admin about it.

If I understand correctly, your routine will clean out all the tables, so that at the beginning of a project, and if you only enter clean data, your database will remain clean.

So, the admin runs this routine on any new project created from a project template. Is that the idea? creating a completely blank database from one that works.

Tony D said:

delete from OPPID_AREA;

If we go ito the OPPID_AREA table and delete the bad areas, will this update the P&ID accordingly (remove from P&ID) when doing a db to P&ID synch? etc....

Ken

Are you from Hatch? Who is the project PAT, and what's his reply?

Yes, I work for Hatch. I am in the Montreal office. I was told that PAT no longer exists. Do you have a PAT resource for your issues?

Yes PAT was renamed, but there is someone taking care of it still. Ask your manager/IT, and find someone in America, I'm too far away from you~

Yes PAT was renamed, but there is someone taking care of it still. Ask your manager/IT, and find someone in America, I'm too far away from you~