Results 1 to 4 of 4
  1. #1
    Join Date
    Nov 2006
    Location
    Indianapolis
    Posts
    90

    Unanswered: alter session set current_schema

    Anyone see a downside to using alter session set current_schema=dataowner;
    in a logon trigger?

    So support users can use SQL without specifying owner

    The other option would be private or public synonyms

    Any thoughts?

  2. #2
    Join Date
    Nov 2003
    Posts
    2,935
    Provided Answers: 12
    If we are talking about a limited/small set of users I'd go for the private synonyms solution.

    I try to avoid public synonyms as much as possible because they tend to create a mess of the database, especially when you are running different applications on the same instance.

    So if you are talking about a huge number of users (where creating the synonyms for each user ist not feasible) I'd go for the logon trigger.

  3. #3
    Join Date
    Nov 2006
    Location
    Indianapolis
    Posts
    90
    Thanks, I have similar feelings about synonyms. I'm going to try out the alter session in a logon trigger, I can't see where it would be a problem.

  4. #4
    Join Date
    Jun 2004
    Location
    Liverpool, NY USA
    Posts
    2,509
    Quote Originally Posted by Indy_tomcat
    Thanks, I have similar feelings about synonyms. I'm going to try out the alter session in a logon trigger, I can't see where it would be a problem.
    remember, it only set the base schema. All the rights to select, update, or delete from the table must still be given to the user.
    Bill
    You do not need a parachute to skydive. You only need a parachute to skydive twice.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •