2 Replies Latest reply on Jul 20, 2016 8:35 AM by Michael Dekoning

EPDM and Standard Parts

John Tonks Jul 19, 2016 10:40 PM

Hi All

I have question relating to the best practice way of handling standard parts.

I have been using EPDM for about 3 years now and have been building up a collection of standard parts. This includes nuts, bolts, bearings etc that get referenced into many different projects.

It only occurred to me recently that each time one of these parts is referenced into an assembly, another "Where Used" record has to be added to the database.

Over time I can imagine that this must bloat the database significantly and I would presume would impact on performance.

So the question is, is it better to create a uniquely named version of the part (you could end having hundreds of files of an M6 nut for example) or to accept that the "M6" nut may have hundreds of "Where Used" references.

The other option I have considered is virtualising all standard parts in an assembly. Are there any downsides to this approach?

Thanks

John

Re: EPDM and Standard Parts

Lee CS Young Jul 20, 2016 12:20 AM (in response to John Tonks)

It's not better to create a new part. Don't worry about the new records. As long as your maintaining your indexes on the database, you won't see a performance hit. This is what a database is built for.

Besides, new part or old part, it's the same amount of rows/records for the reference.
Like Show 0 Likes(0)

Actions
Re: EPDM and Standard Parts

Michael Dekoning Jul 20, 2016 8:35 AM (in response to John Tonks)

I agree with Lee CS Young. I wanted to add that while a record for each where used is created for each reference regardless, if you create new "uniquely named" parts there is a row for each in the documents table that wouldn't be there otherwise. Create once, use many times.
Like Show 0 Likes(0)

Actions

Go to original post