129 results found

1. Support versioning Java within the Oracle database

   Please add support for versioning Java source code within the Oracle database, for example Java Stored Procedures

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Source Control  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Add private DB links

   Add DB links owned by the schema in the snapshot creation / compare options.

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Schema Compare  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Support for IBM Rational ClearCase

   Please add support for IBM Rational ClearCase to Source Control for Oracle

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Source Control  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Richard Mitchell responded

   You can now use any source control system in the v3 release of the tool by using “Working folder” which saves changes to disk and allows you to use external tools to commit and retrieve your changes.

4. Support Perforce as a source control repository for Oracle
   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Richard Mitchell responded

   You can now use any source control system in the v3 release of the tool by using “Working folder” which saves changes to disk and allows you to use external tools to commit and retrieve your changes.

5. Be able to launch Schema Compare for Oracle from within Windows Explorer by clicking on the .ocp project file?

   Received a support request from a customer looking to start or launch a comparison by simply clicking on the project .ocp file.

   Many Thanks
   Eddie Davis

   Redgate Software Ltd
   Technical Support Engineer

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Schema Compare  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Concurrent user licensing

   Add concurrent licensing system to the product so you can use it on Citrix Xenapp.

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Schema Compare  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Schema Compare should be able to ignore system generated names for supplemental log groups

   Schema Compare should be able to ignore names for supplemental log groups. I have many differences on tables that I do not care about like this (the names were generated by GoldenGate):
   ALTER TABLE schemaname.tablename ADD SUPPLEMENTAL LOG GROUP ggs_84245 (columnname) ALWAYS;

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   under review  ·  3 comments  ·  Schema Compare  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Add support for domain indexes in Oracle database (Oracle Text, xmlindex etc)
   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Source Control  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Revert to a previous version

   Please add the ability to revert my schema(s) to a previous from the history tab.

   I understand this is currently possible by checking the version out to a folder, and using Schema Compare to deploy changes, but it would be much more convenient (and cheaper!) from within Source Control.

   5 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Source Control  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. More control over file naming of source-controlled script files.

    It would be good if generating source control files where would be control how files are named.
    Data Compare does not allow joining related objects (like table with alias and indexes), so allowing to change alias name filenames and index filenames patterns would be nice (like prefix+tablename+fieldname for index)

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Schema Compare  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Merge grants (or similar)

    Here is the issue we are having.

    Two developers are working on different instances of the same database schema. If both of them add grants to the same user or role to different objects an issue arises when trying to commit to the repository.

    The user that commits second will have a conflict.

    If they choose the repository's grants for that user, they will lose their changes on their instance.
    It they choose the database's grants for that user, they will overwrite the other user's changes in the repository.

    It would be really nice to have one of these options when dealing with grants:

    1) Treat grants as an attribute of the schema object.
    
    2) Be able to merge grants
    3) Be able to choose individual grants to bring across, and not revoke any.

    Here is the issue we are having.

    Two developers are working on different instances of the same database schema. If both of them add grants to the same user or role to different objects an issue arises when trying to commit to the repository.

    The user that commits second will have a conflict.

    If they choose the repository's grants for that user, they will lose their changes on their instance.
    It they choose the database's grants for that user, they will overwrite the other user's changes in the repository.

    It would be really nice to have one of these options… more

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Source Control  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Data Compare should have facility to compare tables from command line without the need to create a dco file manually
    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Data Compare  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. The comparison does not highlight column changes independly of just order changes. Toad handles this - can redgate?

    The comparison does not highlight column changes independently of just order changes. Toad handles this - can redgate?

    I need to see column differences independently of field order which are not as important. How do I do this in redgate

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. SDK

    as SQL Schema compare sdk

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Schema Compare  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Do not check CheckIn-Scripts for errors optionaly

    Please give the possibility to CheckIn Scripts without error-checking optionaly!

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Source Control  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Foreign Keys not included in comparison if referenced table is excluded by the Ignore Rules Filter

    This presents a problem for fully capturing table DDL definitions that are selected for the comparison

    It is not immediately clear, and may be difficult to detect that FKs are excluded / failed to be captured, unless a full / unfiltered schema comparison is performed.

    There is no indication that the FKs are suppressed and no setting will include them.

    Are there any Schema Compare for Oracle and / or Source Control for Oracle users who would like to see the FK keys that reference Ignored Tables to be included in the deployment script or recorded in the DDL for the table? Or at least be warned that the referencing object is listed in the Ignore Rules?

    This presents a problem for fully capturing table DDL definitions that are selected for the comparison

    It is not immediately clear, and may be difficult to detect that FKs are excluded / failed to be captured, unless a full / unfiltered schema comparison is performed.

    There is no indication that the FKs are suppressed and no setting will include them.

    Are there any Schema Compare for Oracle and / or Source Control for Oracle users who would like to see the FK keys that reference Ignored Tables to be included in the deployment script or recorded in the DDL for… more

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Exclude system-generated interval partitions from comparison and DDL

    For background on Oracle's interval partitioning feature, see chapter 4 of Oracle Database Concept for release 12.2.

    Our practice is to create interval-partitioned tables with the minimum number of partitions necessary to create the table (usually just one partition), and let Oracle create all others as data arrives requiring them. Between test, QA, and production databases, data arrives at different times, giving rise to automatic creation of different partitions. But because these differences are only a side-effect of different contents, they are not relevant, in the same way that differences in system-generated constraint names are not relevant. Changing the partition key or the interval size would require a rebuild.

    Any time there is a CREATE TABLE command for an interval-partitioned table, the command should be limited to only those partitions that are needed to establish the table. In other words, exclude those partitions where DBATABPARTITIONS.INTERVAL='YES', because they are system-generated. The CREATE TABLE command should explicitly list only those partitions where INTERVAL='NO';

    An an example, I have an interval-partitioned table named FMEMBERTENUREMMSNAPSHOT. These are the partitions in my test database:
    C911233@TCRDS_SACRDSD2R.ssdc.kp.org> l
    1 select partitionname, partitionposition, highvalue, interval
    2 from dbatabpartitions
    3 where tablename='FMEMBERTENUREMMSNAPSHOT'
    4 and tableowner='COBIDM'
    5* order by partitionposition
    C911233@TCRDSSACRDSD2R.ssdc.kp.org> /

    PARTITIONNAME PARTITIONPOSITION HIGH_VALUE INTERVAL

    ---

    PARTEMPTY 1 190001 NO
    SYSP937 2 201310 YES
    SYSP968 3 201311 YES
    SYSP966 4 201312 YES
    SYSP973 5 201313 YES
    SYSP933 6 201402 YES
    SYSP970 7 201403 YES
    SYSP967 8 201404 YES
    SYSP931 9 201405 YES
    SYSP932 10 201406 YES
    SYSP935 11 201407 YES
    SYSP977 12 201408 YES
    <skipping many lines for brevity>
    SYSP3318 63 201811 YES
    SYSP3554 64 201812 YES

    If there is a need to generate a CREATE TABLE command, all I really need is shown below, because it is sufficient to establish the table as indicated by INTERVAL='NO' in the query above:

    CREATE TABLE cobidm.rgtemp11090455980 (
    fmbrtenuremmsnpshtik NUMBER NOT NULL,
    dmbrprmyhrnik NUMBER NOT NULL,
    <many columns omitted>
    crdsprcscntlupdid NUMBER NOT NULL,
    CONSTRAINT RGTEMP11090455981 PRIMARY KEY (fmbrtenuremmsnpshtik) USING INDEX (CREATE UNIQUE INDEX cobidm.rgtemp11090455982 ON cobidm.rgtemp11090455980(fmbrtenuremmsnpshtik)
    NOCOMPRESS
    TABLESPACE cobimediumindex),
    CONSTRAINT RGTEMP11090455983 UNIQUE (srcmbrprmyhrnid,srcsnpshtmmnb) USING INDEX (CREATE UNIQUE INDEX cobidm.rgtemp11090455984 ON cobidm.rgtemp11090455980(srcmbrprmyhrnid,srcsnpshtmmnb)
    NOCOMPRESS
    TABLESPACE cobimediumindex)
    ) TABLESPACE cobihcc
    PARTITION BY RANGE (dsnpshtmmik) INTERVAL (1)
    (PARTITION partempty VALUES LESS THAN (190001)
    INDEXING ON
    TABLESPACE cobi_hcc COLUMN STORE COMPRESS FOR QUERY LOW)
    PARALLEL 4;
    ;

    What I am getting today is shown below. This has the effect of forcing the creation of all of these partitions whether I have data that needs them or not, which therefore does not follow my model definition. I have to edit the script to remove the unnecessary partitions.

    --

    -- Script generated by Schema Compare for Oracle 4.0.10.528 on 16/11/2018 07:34:27

    SET DEFINE OFF
    SET SQLBLANKLINES ON

    CREATE TABLE cobidm.rgtemp11090455980 (
    fmbrtenuremmsnpshtik NUMBER NOT NULL,
    dmbrprmyhrnik NUMBER NOT NULL,
    <skipping columns for bevity>
    crdsprcscntlupdid NUMBER NOT NULL,
    CONSTRAINT RGTEMP11090455981 PRIMARY KEY (fmbrtenuremmsnpshtik) USING INDEX (CREATE UNIQUE INDEX cobidm.rgtemp11090455982 ON cobidm.rgtemp11090455980(fmbrtenuremmsnpshtik)
    NOCOMPRESS
    TABLESPACE cobimediumindex),
    CONSTRAINT RGTEMP11090455983 UNIQUE (srcmbrprmyhrnid,srcsnpshtmmnb) USING INDEX (CREATE UNIQUE INDEX cobidm.rgtemp11090455984 ON cobidm.rgtemp11090455980(srcmbrprmyhrnid,srcsnpshtmmnb)
    NOCOMPRESS
    TABLESPACE cobimediumindex)
    ) TABLESPACE cobihcc
    PARTITION BY RANGE (dsnpshtmmik) INTERVAL (1)
    (PARTITION partempty VALUES LESS THAN (190001)
    INDEXING ON
    TABLESPACE cobihcc COLUMN STORE COMPRESS FOR QUERY LOW,
    PARTITION VALUES LESS THAN (201310)
    INDEXING ON
    TABLESPACE cobimediumdata NOCOMPRESS,
    PARTITION VALUES LESS THAN (201311)
    INDEXING ON
    TABLESPACE cobimediumdata NOCOMPRESS,
    PARTITION VALUES LESS THAN (201312)
    INDEXING ON
    TABLESPACE cobimedium_data NOCOMPRESS,

    <skipping many lines for brevity>

    PARTITION VALUES LESS THAN (201811)
    INDEXING ON
    TABLESPACE cobimediumdata NOCOMPRESS,
    PARTITION VALUES LESS THAN (201812)
    INDEXING ON
    TABLESPACE cobimediumdata NOCOMPRESS)
    PARALLEL 4;

    For background on Oracle's interval partitioning feature, see chapter 4 of Oracle Database Concept for release 12.2.

    Our practice is to create interval-partitioned tables with the minimum number of partitions necessary to create the table (usually just one partition), and let Oracle create all others as data arrives requiring them. Between test, QA, and production databases, data arrives at different times, giving rise to automatic creation of different partitions. But because these differences are only a side-effect of different contents, they are not relevant, in the same way that differences in system-generated constraint names are not relevant. Changing the partition… more

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Schema Compare  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Visual Studio extension

    We use TOAD extension for Visual Studio. The one nice thing about that tool is that it integrates the database project with our solution (and TFS), and offers a way to Deploy the database from the scripts that the TOAD extension creates (tables, procedures, etc). It also has a way to run a pre and post deployment scripts. Would be fanstatic if the redgate tools had this as well.

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Pre-script introduction in the scheme compare deployment script.

    Hi , I am trying to understand how to introduce a pre-script ALTER SESSION SET CURRENT_SCHEMA = <> SQL statement in the top of the deployment script which is generated during the schema compare either between source DB vs target DB or TFS vs Target DB.

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  All Oracle  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Reporting Feature in Data Compare for Oracle

    Please add further granularity to the number of rows to include when generating a HTML report. Currently the user can choose to "Only include first 1000 rows" or including all rows.

    Please add further options to select:
    Only include first 10 rows.
    Only include first 1000 rows.
    Only include 'x' number of rows.

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close