This content has been marked as final. Show 3 replies
If you can justify the cost and confusion of building an APEX app who's data ultimately resides in a SQL Database, go for it.. Sounds like you are trying to use a hammer to put screws in.... Use the appropriate tool for the job...
By the time they had diminished from 50 to eight, the other dwarves began to suspect "Hungry".
You can use APEX but you should realize that the performance would be affected since you will be using Database Gateway (and dblink) to perform DML (select, insert, update, delete,etc.). It is not the best approach but it can be a workable one if the not efficient performance is not noticeable.
I think it is a good alternative when the data must exists on a non-Oracle DB when you have staff with APEX skills and can develop an application quickly using those skills.
But, I never have done this approach before, so I cannot tell you from experience.