Settings and activity
4 results found
-
2 votes
An error occurred while saving the comment -
67 votes
An error occurred while saving the comment Denis Cilliers commented
Please add this feature it is critical issue with the dbForge For Oracle.
My current workaround for those that need it
1. Create a local Git Repo
2. Add a Folder in the git Repo called Schema1. File = > New => Project
2. Select the schema file location inside your local repo
3. Select Import Schema objects from the existing database
4. Select the Schema from the Connection
5. Select Include all Objects
6. Select Create a physical folder on the disk for each object type
7. Click CreateOnce the files have been created add them to the repo.
If you follow the same steps again later you will get a updated schema
Over time you will then be able to have a copy of the schema in source control.
and be able to compare the changes over time. -
9 votes
An error occurred while saving the comment Please add this feature it is critical issue with the dbForge For Oracle.
My current workaround for those that need it
1. Create a local Git Repo
2. Add a Folder in the git Repo called Schema1. File = > New => Project
2. Select the schema file location inside your local repo
3. Select Import Schema objects from the existing database
4. Select the Schema from the Connection
5. Select Include all Objects
6. Select Create a physical folder on the disk for each object type
7. Click CreateOnce the files have been created add them to the repo.
If you follow the same steps again later you will get a updated schema
Over time you will then be able to have a copy of the schema in source control.
and be able to compare the changes over time. -
2 votes
Background
-- Propably should have put this one first.
-- The idead was to take the files generated in the New Project Process and use them as a model for comparison.
-- The reason for this is that developers use the SQL files a source for development, and once changes are made to the database these changes need to be synced to files and then updated in the GIT repository.
Commit SQL Files to Git Repo
- we do not have it yet
-- It should not e a big change to allow Git to use the generated files. All we need is a project update, that re-generates the files in the same folder as before.
-- I am currently using this New Project to generate the SQL files and adding then to GIT. This way I have a history of the changes to the database over time.
-- If I use the same folder each time for the New Project Git only updates those files that have changed.
Schema Export to SQL Files
- yes, we have it
-- Yes this is done via the new Project Process.
Schema Compare of Database to SQL Files
- yes, we have it
-- Nope we dont have this feature atm, we can compare datatabase to snapshot and database to database but not to SQL files that are exported
-- This is needed as the main reason is to have the SQL files as the master source in GIT so that when they are retrieved from a Git commit a compare can be made to them.
Generate Create script from SQL Files
- please clarify what exactly you mean, do you mean conversion of some stats or something else?
-- Currently the Generate can only be performed against a databse, the idea was to allow the SQL files to be a source of a model that can then be used as a means to generate a difference
Generate Diff Script from SQL Files
- we do not have it yet
-- Nope we dont have a diff script from SQL files only existing Databases or Snapshots
Deploy Create Script to Database
- also, not clear, but you can use Execute large script
- This is the schema compare tool output create scripts that are automated to bring a database up to the needed schema that is in the GIT commit
Deploy Diff Script to Database
- After synchronizing the two databases, you can immediately run a script to align them.
-- Nope we dont have this facility, it would be the last step to allow the sync script from the Deploy Create step to be run against a target database.
-- Once the sync has been completed a compare of the two can be run and a report generated to confirm that the sync as performed.