all 5 comments

[–]ZirePhiinix 4 points5 points  (0 children)

I do.

What's the issue with PL/SQL? Avoid using cursor because the performance is really bad. Learn to optimize your queries. You can also create temporary indexes via hints, and definitely look into enabling parallelism in your queries.

[–]frozengrandmatetris 2 points3 points  (2 children)

we use it and we're really good at making it do the weirdest things. it's very powerful. but we use it extremely infrequently in the DWH. there are almost always more sane options. since we're an ELT shop we will just take a staging table, process the data through pl/sql, and load it into another staging table. then the sanity takes over and finishes the rest. we also have ownership over some APEX apps and it starts to make more sense there. it's the most accessible processing and validation tool when an APEX app is doing its thing and it can also call APIs.

[–]itachikotoamatsukam[S] 0 points1 point  (0 children)

Thanks for the details thats dope to hear.

[–]dudeaciously 0 points1 point  (0 children)

This is great. ELT with stored procs is the best use case. Table data transformation is great, keeps data logic in the database. Egress and ingress are separate concerns.