how understanding old, obsolete database information enlarged controlling system?


what possibilities programmer hoop information magnitude used nonetheless can't simply deleted since during slightest observant still requires it?



some examples i am pondering of:




  • discountinued stipend forms comparison years university

  • unused currencies (e.g. italian lira)

  • names left countries (e.g. austro-hungary, ussr)



some biased solutions activity flags, activity periods, priorities cognisance nonetheless any means box case preference tough know forms entities need special handling.



may there settlement pattern problem.



conclusions: (based answers far)




  • if aged information creates bland work challenging vast database, partitioning helpful. oracle's outline theme .


  • from indicate perspective engineer taxonomy gives credentials information.




Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members