Schema Compare/Source Control
So, the deployment process that I have been using to go from the repository to our production database server is to have the developers commit their changes to an SVN reposority via Source Control for Oracle. Then, they let me know which revision of the database to deploy to production.
I then use TortoiseSVN to Checkout that version of the repository. I then compare that scripts folder with where I would like to deploy that revision using Schema Compare.
However, when I open the scripts folder, I always get the notification:
This scripts folder is in an old format. Upgrade the folder to use it in comparisons.
When I click the Upgrade link, it removes the .svn folder and touches every file in the scripts folder. So, it doesn't change the repository, so the next time I checkout from the repository, I have the same issue.
I am wondering a few things, is there a better practice than how I am doing the deployments from the repository (realizing that I don't always want to pull the head revision from SVN)? Or is there a setting that will ignore the .svn folder so when Schema Compare touches all the script files it will allow me to easily check in the changes?
Finally, it would be a GREAT feature to have the repository be a choice instead of just "Database", "Snapshot", and "Scripts Folder" from the schema compare tool.