Custom Reference for Attributes

Discussion created by mikeloria on Dec 3, 2012
Latest reply on Dec 12, 2012 by Ahmad Fattahi

I believe that a look up table in AF should be a finite number of records?  I have a proposed business case where the table would continue to grow where each record represents a unique product and the product ID is referenced. This table would continually add new records at a rate of about 10,000 per month. I see this as an issue when we wish to view data from 6 months ago because the records would be need to be cached from the query which would cause a very large periodic pull from the database and would be a performance problem. I believe that the best solution would be to just make the attribute type to be PI tags and write to them for each new product. This way the data is archived in PI and there is no issue when we need to go back several months.


Is there another alternative to writing this data to PI tags. I recall something about custom data references but i am not sure how well that would fit in this case.


Thank you in advance for your advice.