Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
I am new to CREO and Windchill.
We are running CREO 3.0 M090 and Windchill 11.0.
Is there a setting in Windchill 11.0 that deletes all previous versions of a part once that part, Assembly or Drawing is release?
Solved! Go to Solution.
No there is nothing like a purge command in Windchill like can be done with a native OS filing system.
Also, the iterations should not be in your SQL database but in your file fault, which in my case is on my Windchill server, not my Oracle server.
If you are storing your files in the DB, please reconsider your setup and get them stored in external file vaults.
Windchill Archive only works on revisions. If you have revision 1 released (1.5) and then revise it to revision 2 (2.1) you can then run the archive utility to move the 1.x versions offline.
Careful with your terminology of windchill.
Version is a combined Revision and iteration. (2.4 or D.8)
Revision is controlled by a table in most installs. (A, d, 0, 3 or 0, 3, A, G)
Iteration is incremented automatically every time a file is checked-in to the Windchill common space.
Actually it does not matter as NO versions, revisions or iterations are deleted/removed from Windchill automatically.
You can run an archive routine that will backup and remove the actual files from your file server for older revisions (and all if a revision's iterations).
Ben,
I stand corrected.
I guess what Is was trying to ask is this:
this would save space on the Winchill/SQL Server database.
No there is nothing like a purge command in Windchill like can be done with a native OS filing system.
Also, the iterations should not be in your SQL database but in your file fault, which in my case is on my Windchill server, not my Oracle server.
If you are storing your files in the DB, please reconsider your setup and get them stored in external file vaults.
Windchill Archive only works on revisions. If you have revision 1 released (1.5) and then revise it to revision 2 (2.1) you can then run the archive utility to move the 1.x versions offline.
Ben,
thanks for your input.
I will go back and verify my settings are correct.