Hi all,
Can anyone recommend on a Source-control/Version-con
We are currently using TOAD's team-coding, integrated with Microsoft VSS, but only since we are not aware of any other means of keeping code history.
I am looking for anything that might be suitable some piece of software, that helps keeping history of PL/SQL code, optionally helping to keep also history of table structure. This software might also be able to maintain multi-versions/branches, and also automatic Schema script generation.
Anything you know of would be great.
Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Something free, something easy, or something fast? <grin>
With 10g I love using DataPump to extract the DDL as metadata, and it can generate the re-create scripts automatically. The poor person's approach to tracking package changes can be as simple as saving them them with a consistent date-time suffix. We then track which version is in a release by means of a spreadsheet.
Business Accounts
Answer for Membership
by: jtriftsPosted on 2007-07-30 at 04:09:21ID: 19591486
Hi,
Not sure exactly what you mean in terms of "keeping a history". Most SCM (Source Control Management) tools will store the "delta" when making a change -- i.e. it stores the difference between successive revisions of a file. Examples of this include good old Unix RCS, PVCS, CVS etc.
With CVS and PVCS for example, you can run a diff report between versions in a single archive, a version in the archive and on the file server, or in different archives. When you make changes to code however, that is the time to be documenting what the changes are. Ideally you put these into the version history comments when you check the object back into the repository.
Generally, with SCM tools though, you get what you pay for. Subversion, for instance is free to use are many versions of CVS interfaces -- but of course you won't get the support that you get when you pay a premium for example, when you license PVCS.
I don't know of ANY SCM tool that keeps track of table/schema type changes -- as this would need to be more "intelligent" than current SCM tools are. This is due to the fact that an SCM tool is generally software agnostic -- i.e. it does not understand the detail of underlying objects you are storing. To PVCS, what is the difference between a SQL script which creates tables, a PL/SQL script which creates a package/procedure/function
That said, if you use a tool such as Oracle DEsigner, you can develop successive versions of design which CAN be versioned within its own repository and then you can generate the scripts which build the database (and its schemas) -- but still this doesn't meet your requirement.
Do you think you could explain a bit more about what you want, and WHY and WHAT such a feature list would offer you? It could be that your question is for a more specific purpose and that we might be able to find an alternative to meet the *real* requirement.
REgards,
JT