Comments
Sort by recent activity
As noted we deploy our schemas by the schema owner -- using RedGate combined w/ source control (Source Control for Oracle) that should give us nice per schema versioned representations of the individual schemas. -- If using the super user approach, we'd have a multi-schema model to manage / untangle which could get complicated / messy rather quickly (e.g. too many developer DBAs in the kitchen). -- Right now that appears to be the only way to manage multi-schema deployments with a single scripted deployment. (I have not tried that approach so I'm not sure how well the inter-dependency is managed.) What would be really nice is: 1. a way to specify inter-dependencies between distinct schema models (i.e. source scripts) so that they could be deployed in a coordinated way. 2. a way to specify logon info for multiple schema owners (so the owner deploys DDL to their own schema) While not an every day occurrence, the scenario that requires a multi-schema deployment w/ coordinated steps between each does come up. / comments
As noted we deploy our schemas by the schema owner -- using RedGate combined w/ source control (Source Control for Oracle) that should give us nice per schema versioned representations of the indiv...
Here is a link for the privs required by Schema Compare for Oracle: https://documentation.red-gate.com/sco5/requirements/permissions-required-to-use-schema-compare-for-oracle In our shop we manage deployment by schema owner -- the owner has the necessary grants to deploy into their own schema only. If you want to have a super user that can deploy to any schema see the above for the list of necessary create any privs. - martin / comments
Here is a link for the privs required by Schema Compare for Oracle:https://documentation.red-gate.com/sco5/requirements/permissions-required-to-use-schema-compare-for-oracleIn our shop we manage de...
Some SQL IDE's have the ability produce a data model diagrams of limited utility. For MS SQL I think SQL Server Management Studio has something built-in. On the Oracle side SQLNavigator, Toad, or PL/SQL Developer have limited capabilities. To really create and manage data models used as the starting point for development (or to reverse engineer a complex schema/database) turn to a full-feature data modeling tool like Idera's (Embarcadero) ER/Studio, or ERWin. / comments
Some SQL IDE's have the ability produce a data model diagrams of limited utility.For MS SQL I think SQL Server Management Studio has something built-in.On the Oracle side SQLNavigator, Toad, or PL/...
Issue is resolved in release 5.2.5.1424 / comments
Issue is resolved in release 5.2.5.1424
Associated bug ID: OC-1037 / comments
Associated bug ID: OC-1037
I second the importance of resolving this issue. / comments
I second the importance of resolving this issue.
While on this thread can someone please explain the purpose of the Transients local working copy / how it is used vs. the Working Base? / comments
While on this thread can someone please explain the purpose of the Transients local working copy / how it is used vs. the Working Base?
The conflict arises because the object(s) in question in both your local source and your repository have been updated (independently). SVN can't identify which edit takes precedence, so your local working copy is "conflicted". Source Control allows you to accept either the working copy or the repository copy to resolve the conflict. You can also resolve the conflict manually (use caution). Source Control actually maintains two working copies -- one under Transients and one under WorkingBases: C:\Users\<Username>\AppData\Local\Red Gate\<Source Control For Oracle Version>\Transients C:\Users\<Username>\AppData\Local\Red Gate\<Source Control For Oracle Version>\WorkingBases Note: The specific project names have cryptic names. They can be resolved by looking at the XML properties files under C:\Users\<Username>\AppData\Local\Red Gate\<Source Control For Oracle Version>\: LinkedDatabases.xml XPath for a quick dump: //LinkedDatabaseList/value/concat("DB ID: ", DatabaseId/ServerAndInstanceName, ' | RepoType: ', ISrcCLocation/@..., " | Repo URL: ", ISrcCLocation/RepositoryUrl, ' | WorkSpace: ', IWorkspaceId/RootPath, ' | Transient: ', ScriptTransientId/RootPath) The DB IDs can be resolved to the project name in ConnectionStore.xml: Xpath: //DatabaseConnections/value/concat("Project Name: ", ProjectName, " | DB ID: ",ConnectionGuid) / comments
The conflict arises because the object(s) in question in both your local source and your repository have been updated (independently).SVN can't identify which edit takes precedence, so your local w...
Additional clarification on this issue: My actual column is an XML column. The LOB reference points to a shadow column that Oracle creates for XMLType columns behind the scenes -- and not the actual column name. See attached file, RG_ScourceControlOracle_sample_DDL_SQL.txt, for sample DDL (you will need to adjust the tablespace arguments for your environment) that illustrates this behavior. The shadow column appears in the user_tab_cols dictionary view, but not in the user_tab_columns dictionary view. I would expect the DDL captured by RedGate to reference the actual XML column name vs Oracle's shadow column. As a side note a lob_segment name (if specified) -- for any type of LOB column -- is not captured in RegGate's DDL generation.even if the LOB and tablespace options are selected. ScourceControl differences identified -- none are visible: (same results if using SchemaCompare) [image] / comments
Additional clarification on this issue:My actual column is an XML column. The LOB reference points to a shadow column that Oracle creates for XMLType columns behind the scenes -- and not the actua...
So in a future release is there planned support for fine-grained storage clause attributes?
Can you provide any insights on the time frame of when these features might be added?
As an example in our environment tablespaces are locally managed and we only want to specify tablespace info (and partition info if applicable)
Attempting to sync the complete storage clause info across instances may be undesirable) / comments
So in a future release is there planned support for fine-grained storage clause attributes?
Can you provide any insights on the time frame of when these features might be added?
As an example in ou...