Skip to content

Oracle

Welcome to our Oracle solution feature suggestion site. Find out more information about our current offering at www.redgate.com/oracle.

If you have any questions, need help, or have found a bug, please visit the forums at forum.red-gate.com/categories/oracle-tools.

Oracle

Categories

JUMP TO ANOTHER FORUM

(thinking…)

How can we improve our Oracle solution?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

26 results found

  1. SID is limited to 8 characters

    The SID for my oracle instance is 10 characters. The connection wizard only allows 8 characters so can't use the product.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Source Control  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Allow us to choose the schema prefix

    We noticed that all objects have a prefix in front of it.
    The prefix happens to be the same as your folder name. I would prefer it if it was the same as the schema name, or NULL. Preferably give us the right to choose a prefix name.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Source Control  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    completed  ·  Richard Mitchell responded

    I believe you can do this in the latest version of Source Control.

    Either you can make your schema name the same as the folder when you setup your project.

    Or you can now access the options via right-click on the project on the projects page and select “Edit comparison options…” and use the option “Exclude schema names”

  3. Data should be a part of the version control for metatables

    Some tables are metatables involving data/information connected to the software releases. The Source Control utility should have a possibility of setting a switch on the tables, turning data compare on. This way you could include data for these tables in the version control.

    131 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    14 comments  ·  Source Control  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    completed  ·  Doerte responded

    We just released static data support for Source Control for Oracle.

  4. The code comparison window should be resizable vertically.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Source Control  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    completed  ·  Anonymous responded

    Thanks Leigh, this should now be the case in the latest beta release

  5. Match source when creating repository files.

    When checking in a new package from the database, the schema name in references throughout the package is changed to have double quotes around it. Then when a change is made on the file, the entries from the database without the double quotes do not match the entries from source control with the double quotes. It seems that this difference alone isn't enough to show the comparison as different, but when another difference exists, these entries are all flagged as different. To resolve this, the double quotes should not be created in the first place.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Source Control  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    completed  ·  Anonymous responded

    Thanks Leigh. We believe this is fixed in the latest beta release, please do advise.

  6. Put package header and body in seperate files.

    When a repository is created from the database, both the package header and the package body are placed in a single file. It would be more usable if the spec and body were in separate files in the same folder with a .pks or .pkb extension respectively.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Source Control  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    completed  ·  Neil Anderson responded

    this will be in the next release of Schema Compare and Source Control for Oracle

2 Next →
  • Don't see your idea?