A database application I'm working with uses Oracle scheduled jobs to perform certain tasks. The DBA insists that hard-coding the schema name in the procedures that organise these jobs improves performance, but I can't see how it makes any difference. (I'm not even sure why it's necessary to have the schema name in there at all - the procedures run by the jobs are always in the same schema as the the job definer.)

Can there possibly be any truth to this? In general, does specifying the schema name make any difference when calling a procedure in the same schema as the connected user?

  • There is no performance impact, but it is a sure fail of you have to import that job under a different schema. When job accesses objects in the same schema, there is no need to prefix. In a way your DBA may be right, that prefixing schema name is better for name resolution than synonyms, but in your case it doesn't apply. – Raj Apr 10 '14 at 19:27

There is no performance impact.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.