Skip to Main Content
  • Questions

  • ETL schemas on a production database

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Michael.

Asked: August 03, 2018 - 12:06 am UTC

Last updated: August 03, 2018 - 2:42 pm UTC

Version: Oracle Database 11g

Viewed 1000+ times

You Asked

I need to support an ETL app that will use a production database clone as the data source. I'd like to put the ETL app's two schemas (target tables and pl/sql) on the production database, to limit ETL app set up that needs to be done on the clone after the production database is cloned. Is this plan bad practice? The ETL target tables on the production database would be empty and the accounts locked.


and Chris said...

The ETL target tables on the production database would be empty and the accounts locked.

If you're not using these tables, why are you placing them on the production database at all? What's this gaining you?

You shouldn't put anything on a database that doesn't need to be there. Particularly if this for a mission-critical application. It increases the chances of security loopholes and mistakes.

So it sounds like a bad idea to me - unless you have a strong justification for doing so?

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Feedback to Chris Saxon's response

Mike Harris, August 17, 2018 - 4:24 pm UTC

Thank you for the feedback to my question. I will stick with the guidance that you have provided.
more

Connor and Chris don't just spend all day on AskTOM. You can also catch regular content via Connor's blog and Chris's blog. Or if video is more your thing, check out Connor's latest video and Chris's latest video from their Youtube channels. And of course, keep up to date with AskTOM via the official twitter account.

More to Explore

Design

New to good database design? Check out Chris Saxon's full fundamentals class.