On 16, April 2010, at 16 Apr 13:42, Blue Bull wrote: > The Legacy tables are hug, being used by umpteen other apps. hence, i > want to search once and store data within application table for > processing as and when required. > Is it viable to create models in my app, migrate search data for each > result row into the app table? Or is it just better to create dynamic > views within oracle DB everytime a query is initiated and use this data > for reporting purposes?
When I had the same issue (except I also had an MS SQLServer in the mix as well as my RoR app's PostgreSQL database) I did a mix of things. 1) views on the Oracle server for stuff that can be kept remote 2) Local copy of static Oracle data done through a replication deamon that I wrote 3) Queries on the local data for speed Mikel Lindsaar http://rubyx.com/ http://lindsaar.net/ -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
