Database source code control or version management

Hi all,
I work in a data warehouse development project, where database schema changes form majority of development work. As a development DBA I look after ensuring that all the database schema changes are version controlled properly.
We currently use CVS as a source code control system. We can use CVS well enough where stored procedures, functions and packages are involved. But when it comes to table definitions, we are finding use of CVS bothersome.
Hence I would like to know, which tool are you using for version control of schema changes. Any links to best practices on DB version control would be much appreciated.

I think Oracle have introduced something in 11g for version control. Also you can use third party Software like ERWIN. You can also explore Oracle Data Modelling software which is Beta currently.
Regards

Similar Messages

How to use Source Code Control for Large Application?

Hi, All!
I would like to collect knowledge about "best practice" examples for using Source Code Control and project organization for relative large application (let's say approx 1000 SubVIs).
Tools used:
LabVIEW 8.0
CVS Server
PushOK CVS Proxy Client
WinCVS
With LabVIEW 8 we can organize large project pretty well. This described in article Managing Large Applications with the LabVIEW Project.
I have read this article too: Using Source Control Software with LabVIEW In this Article Source Safe used, but with PushOK all looks nearby the same and works (some tricks for compare function are required).
Example. Two developers working together on same project. Internally project is modular, so one developer will work with module "Analysis", and another one with "Configuration" without interferences. These modules placed into Subfolders as shown in example above.
Scenario 1:
Developer A started with modification of module "Analysis". Some files checked out. He would like to add some SubVIs here. So, he must also perform check out for the project file (*.lvproj), otherwise he cannot add anything into project structure.
Developer B at the same time would like to add some new functions into module "Configuration". He also needed to check out project file, but this file already checked out by Developer A (and locked). So, he must wait until lvproj file will be checked in. Another way is mark *.lvproj files as text files in PushOK, but then one of developers will get conflict message by checking in and then merging will be necessary. This situation will coming very often, because in most cases *.lvproj file will be checked out all the time.
Question: Which practice is better for such situation? Is Libraries better than folder for large project?
Scenario 2:
Developer C joined to the team. First, he must get complete project code for starting (or may be at least code of one Library, which assigned to him).
Question: How it can be done within LabVIEW IDE? Or WinCVS (or other SCC UI) should be used for initial checkout?
Scenario 3:
Developer D is responcible for Build. Developers A,B,C have added lot of files into modules "Analysis", Configuration" and "FileIO". For building he need to get complete code. If our project splitted into folders, he should get latest *.lvproj first, then newly added SubVIs will appear in Project Explorer, then he should expand tree, select all SubVIs and get latest versions for all. If Project organized in Libraries, he must do the same for each library, isn't?.
Question: Is this "normal way", or WinCVS should be used for this way? In WinCVS its possible with two mouseclicks, but I prefer to get all code from CVS within LabVIEW IDE recursively...
That was a long post... So, if you already working with LabVIEW 8 with SCC used for large project, please post your knowledge here about project structure (Folders or Libraries) and best practices, its may be helpful and useful for all of us. Any examples/use cases/links etc are appreciated.
Thank you,
Andrey

Regarding your scenarios:
1. Using your example, let's say both developers checked out version 3
of the project file. Assuming that there are only files under the
directories in the example project, when Developer A checks in his
version of the project, there will be new files in one section of the
project separate from where Developer B is working. Developer B,
notices that there is now a version 4 of the project. He needs to
resolve the changes so will need to merge his changes to the latest
version of project file. Since the project file is a text file, that is
easy to do. Where an issue arrises is that after Developer B checks in
his merged changes, there is a revision 5. When Developer A and B go to
make another change, they get the latest version which will have the
merged changes to the project file but not the referenced files from
both Developer A and B. So when A opens version 5, he sees that he is
missing the files that B checked in and visa versa. Here is where the
developers will needs to manually use the source control client and,
external to LabVIEW, get those new files.
Where libraries help with the above scenario is that the library is a
separate file from the project so changes made to it outside of the
project do not require the project to be modified. So this time, the
developers are using a single project again which time time references
two libraries. The developers check out the libraries, make changes to
the libraries, and then check those changes in. So when each developer
opens the project file, since it references the project file, the
changes to the library will be reflected. There is still the issue of
the new files not automatically coming down when the latest version of
the library is obtained. Again, the developers will needs to manually
use the source control client and, external to LabVIEW, get those new
files. In general, you should take advantage of the the modularity that
libraries provide.
2. As noted in the above scenario, there is no intrinsic mechanism to
get all files referenced by a LabVIEW project. Files that are missing
will be noted. The developer will then have to use the source control
provider's IDE to get the initial contents of the project (or library).
3. See above scenarios.
George M
National Instruments

Source Code Control - Check in problems

Some of my vi's have been marked as "Server copy has changed" and some have even been marked with "both local and server copies have changed". When this is the case I cannot find any way to check in my VI without getting an error. Looking for a work around - help.

kh,
Which version of LabVIEW are you using? Built-in SCC have been rewritten from 6.0 to 6.1 and there are different issues related to each version.
With 6.0 I have encoutered a bug that wrongly checked most of my VIs as "local copy has changed" as soon as they are in memory with panel closed. I worked with NI Support and we found no workaround. Unfortunately, this behavior stayed even when the VIs were upgraded in 6.1 so that my problem was a dead end. I switched with great success to CVS, another source code control software.
I do not use 6.1 but if you do, make a search on NI's site and you'll find hits that address a SCC bug. If I remember correctly, checking out a VI, making a small change and checking it in again often solved the problem.
G
ood luck.
LabVIEW, C'est LabVIEW

RE: Using a source code control system

Thanks Shane and everybody for the replies.
My *.cex files have the correct "begin CLASS;" entry. Below is my fscript
file
that I'm trying with Forte 2.0.E.2 NT version:
setWorkspace ktCheckBoard
open
findproj sample1
cd c:\forte_cs\install\bin
compile sample1_sysadm.cex
importplan sample1_sysadm.cex (>>> It failed right here)
Khanh
From: Shane Howlett
To: forte-users
Subject: RE: Using a source code control system
Date: Wednesday, November 13, 1996 9:54PM
Hi Khanh,
In regards to your compile error...
We found that an interesting difference between versions 2.0.D.x and 2.0.E.x
was with the first line of an exported .CEX file.
A la ...
2.0.D line 1: begin;
2.0.E line 1: begin CLASS;
It caught me out. Just insert or remove the word CLASS using a text editor
depending on your version of Forte.
As for version control, we have been retaining workspace export files
(wascally WEX files!) as backups and plan to make greater use of Baselining
in
the repository. In terms of securing our environment, this approach
essentially meets our needs.
Shane Howlett
The Hydro.

Thanks for your help. That works.
-khanh
At 11:20 AM 11/14/96 -0800, you wrote:
>
Hi Mike,
Thanks for the reply. I think that was what I did.
Below is my fscript input file:
setWorkspace ktCheckBoard
open
findproj sample1
cd c:\forte_cs\install\bin
compile sample1_sysadm.cex
importplan sample1_sysadm.cex (It failed at this step)'importplan' is unnecessary: 'compile' has compiled the .cex file into your
project. importplan is failing beacuse it expects to see an entire plan.
Mike
Mike Schilling ([email protected])
Forte Software, Inc.

Help needed to use Source code control system

Hi all
I am working on Suse 9.2 and I use JSP and Servlet in my project.I like to use Source Code Control System (SCCS) . But I have no idea about that.I need some help to initiate my project.
Thanks in advance.
-jegan

I don't know this "SCCS" but I advice you to use Subversion as it is widely used open source standard.

How to setup source code control with StarTeam

Hi,
Could anyone please tell me what should I do to set up the source code control?
My company use StarTeam Borland as a source code control tool. I try to set this as a Source Control for Labview by go to SourceControl category ins the Options setup, but I cannot select anything form the list of provider name. Do I have to do any extra step to make it right?
Best regards,
Thang Nguyen
Message Edited by THANG NGUYEN on 08-12-2009 05:23 PM
Attachments:
SourceCodeControl.JPG ‏64 KB

Read this: Source Code Control Provider Does Not Appear In LabVIEW Options. (A simple search would have yielded this.)

Database Source Code Synchronization with PVCS

Hello All,
I would really appreciate your ideas/suggestions on developing, implementing the following requirement.
I am in the process of developing a mechanism to validate the database procedure source code in the application PVCS library, that matches the source code used for QA and PRD environments. The objective is to assure that production version of stored procedure code is the correct / matching version with PVCS, QA and PRD.
Database: Oracle 9i
Source Control System: PVCS
Database Objects: Stored Procedures
Other Questions:
- Do you know any PVCS API's to read the files?
Thanks, Madhavi

Hello All,
I would really appreciate your ideas/suggestions on
developing, implementing the following requirement.
I am in the process of developing a mechanism to
validate the database procedure source code in the
application PVCS library, that matches the source code
used for QA and PRD environments. The objective is to
assure that production version of stored procedure
code is the correct / matching version with PVCS, QA
and PRD.This is going to take a lot of work and I am not even sure that is is deterministic. And it is easily handled by the correct process control as well.
The following process control steps allow this.
- Developement ONLY delivers scripts for database changes. Thus table changes, data changes, new procs, old procs, what ever are delivered as scripts and are checked into version control.
- QA does NOT use anything that is not in the version control system. No disks, memory sticks, emails, etc (and in particular QA does NOT use developement database servers for testing.)
- QA are the ONLY ones allowed to install anything to production. This includes all the DBAs and it includes "emergency" fixes (which usually greatly diminsh if the above is followed and QA is actually testing stuff.)
The last step can be enforced either by simply disallowing change access to production machines except for QA and non-developement (MUST be non-developement) admin.
But if you insist, people have been interfacing programmitically with Oracle and PVCS for years. You can search the net for thousands of these. I suspect that you will find that Perl is used a lot in this (but that could be my own bias.)

Source Code Control for Java development in 6.20

I am new to Java development. How do you control source code (versioning/transport) for Java development with the base R/3 is 6.20. I believe Java Development Infrastructure (JDI) is only available in 6.40. Is this the correct statement? Anyone that has work on 6.40 with Java can explain?
Let say we have this setup:
Applications are in 6.20
Portal will be EP 6.0
Do we need Web AS 6.40 to develop Java for Portal with base R/3 of 6.20. Or we can use Developer Studio to create Java accessing R/3 6.20 and display in Portal 6.0. If this is the case, how do you manage transport is you are not using JDI in 6.40.

Hi Nablan,
I believe you are development J2EE applications. JDI only runs with WebAS 6.40 which supports J2EE spec. 1.3. The developed J2EE archive will not be able to deploy to WebAS 6.20 which only supports J2EE 1.2 spec. So if you want to deploy the created software build from JDI and deploy it to WebAS 6.20, then the answer is unfortunately no.
But, if you just want the Portal be able to display your application in an iView inside, then maybe you can just develop and deploy your application to the WebAS 6.40 system. Then create an iView in your EP to point to the app in the 6.40 system. That way your app will not need to deploy to WebAS 6.20.
Regards,
Marc

JDK source code of earlier versions

Hi,
I'm doing some research on code clones. I wrote a tool to categorize code clones and i would like to test it on several open source projects. I found a paper of another researcher that did similar research in the past and he also used several open source projects. To compare my results with his results i'd like to take the same projects. One of them is JDK 1.1.5, but i can't find the source code on the internet. I only found the source code of JDK 1.5 and 1.6. I'd like to have the source code of version 1.1.5 or at least a version earlier than 1.5. Can anyone help me?
Message was edited by:
KinkyHagar

Check the src.zip file in your jdk folder.

Having Problem in access to Source Code Control System (URGENT help needed)

I am using JDeveloper 9i first time. The repository is in Oracle 8i.
I have established a connection from JDeveloper 9i to Oracle 8i repository running on Sun Solaris.
We have created a shared area and my colleague have checked-in some files. I have all access to shared area and I can see the checked-in files, but I am not able to check-out to the local folder.
I need help to resolve this problem urgently. Please consider this as an SOS call. Thanks

Hi,
The JDeveloper help system strongly recommends that you don't use shared workareas in this way. In fact, it's not possible in the beta release of JDeveloper to work this way at all, because there is no way for you both to get the files on to your file system in a way that JDeveloper will recognize.
The JDeveloper documentation on Repository is a very good source of information on the best way to organize developer workareas (particularly the section on best usage recommendations). The Repository is a very complex product originally intended for much more than just source control and there are many ways of using it. We have necessarily had to focus on a subset of this functionality in JDeveloper, mainly to keep the UI from being excessively complex for new users.
Here's a summary of the way we recommend working:
o Create a workarea in the RON which will be used as the basis of developer workareas (developers will not actually use this workarea directly). Make this workarea shared by granting access rights to the PUBLIC role.
o Each developer uses the Workarea wizard in JDeveloper (Source Control->Configure... in the beta release) to create a developer workarea based on the shared workarea.
Thanks,
Brian
JDeveloper Team
null

RE: Using a source code control system with...

Hi Khanh,
In regards to your compile error...
We found that an interesting difference between versions 2.0.D.x and 2.0.E.x
was with the first line of an exported .CEX file.
A la ...
2.0.D line 1: begin;
2.0.E line 1: begin CLASS;
It caught me out. Just insert or remove the word CLASS using a text editor
depending on your version of Forte.
As for version control, we have been retaining workspace export files
(wascally WEX files!) as backups and plan to make greater use of Baselining in
the repository. In terms of securing our environment, this approach
essentially meets our needs.
Shane Howlett
The Hydro.

Thanks for your help. That works.
-khanh
At 11:20 AM 11/14/96 -0800, you wrote:
>
Hi Mike,
Thanks for the reply. I think that was what I did.
Below is my fscript input file:
setWorkspace ktCheckBoard
open
findproj sample1
cd c:\forte_cs\install\bin
compile sample1_sysadm.cex
importplan sample1_sysadm.cex (It failed at this step)'importplan' is unnecessary: 'compile' has compiled the .cex file into your
project. importplan is failing beacuse it expects to see an entire plan.
Mike
Mike Schilling ([email protected])
Forte Software, Inc.

Version management for SAP Screens?

Hi,
I need to do version comparison for sap screens .
My source system is R/3 4.7 & Target system is ECC 6.0.

For front end SAPUI5 CODE in Elipse or RIVER RDE you can use GIT which is pretty standard way of doing code management. Once you push the code to GW it is in BSP and then you dont have much control on the version management side. If there are multiple developers working on front end code then you can push to GW using ABAP Team Provider plugin in Eclipse that pushes the sapui5 code to BSP via workbench request and once 1 developer is done then he/she will submit the code. the next person then does the GET from GW into their Eclipse to get the latest version of source code. But if there are 10 changes to the sapui5 code then on front end side you should use GIT or BitBucket or MS Team Share kind of source code control tools that integrate with ECLIPSE.
For oData Service you can do version management in ABAP stacks. you can have multiple versions for your service and then deploy to prod the one that you are sure of. Std change management can be used for backend GW service development.
thanks
Ashish

JDeveloper integration with Serena PVCS Version Manager

I have seen that Oracle JDeveloper 10.1.3 now supports Serena Dimensions for versioning. What about Serena PVCS Version Manager 8.1? Are there any plans to integrate JDeveloper with the PVCS Version Manager?

Hi all,
Ward - Brian is absolutely right. As I said in my first posting on this topic (above), we have
not yet developed an extension for JDeveloper to enable users to work with PVCS Version
Manager, which I believe is a specific product, rather than an interface.
This is why I'd greatly appreciate it if you could possibly provide more details of this Interface
and indeed what Oracle support for PVCS with JDeveloper Merant referred to. Please see my
first posting above for more details.
Brian - I'm sorry you do not agree with our approach of using the open published SCM Framework
to build your own extensions for using JDeveloper with other source code control tools than those
we support.
In an ideal world, we would have been able to offer support for every source code control tool on
the market with our first release of 9i JDeveloper. We were very keen to be able to achieve this and
we still plan and are currently looking into supporting more tools going forward and as many tools as
possible in the long term.
Unfortunately, we only have limited time available for each release and based on the feedback we
received, after our committment to support Oracle9i SCM, CVS and ClearCase were the most requested.
Therefore, we tried to reach a compromise to enable users to provide their own support for a specific
tool should they wish, if they did not use any of those tools supported. Indeed, our research suggests
that the market for source code control tools is quite fragmented and that customers use a wide range
ot tools. So, we decided to publish our own SCM Framework, the same one we used for the SCM, CVS
and ClearCase support, in order to help users build their own extensions in a similar way to ours.
Hope this helps,
Regards,
Dominic Battiston
JDeveloper Product Management
Oracle Corp

SAP Fiori: Version Management for SAP Gateway Enhanced Services & SAP UI5 Application

Hello Experts,
Greetings!!
I would like to check how version control is achieved for SAP Fiori app extensions. Or while enhancing the SAP UI5 applciation or enhancing a SAP netweaver gateway backend service for Fiori App.
I would appreciate your inputs. Thanks in Advance.
Sudhanshu ~
Tags edited by: Michael Appleby

For front end SAPUI5 CODE in Elipse or RIVER RDE you can use GIT which is pretty standard way of doing code management. Once you push the code to GW it is in BSP and then you dont have much control on the version management side. If there are multiple developers working on front end code then you can push to GW using ABAP Team Provider plugin in Eclipse that pushes the sapui5 code to BSP via workbench request and once 1 developer is done then he/she will submit the code. the next person then does the GET from GW into their Eclipse to get the latest version of source code. But if there are 10 changes to the sapui5 code then on front end side you should use GIT or BitBucket or MS Team Share kind of source code control tools that integrate with ECLIPSE.
For oData Service you can do version management in ABAP stacks. you can have multiple versions for your service and then deploy to prod the one that you are sure of. Std change management can be used for backend GW service development.
thanks
Ashish

PVCS Version Manager Interface to Jdeveloper -- need help with install

Several of our developers are using Jdeveloper and we need to know how to install the PVCS Version Manager interface to JDeveloper.
I have already contacted Merant, the vendor for PVCS Version Manager and they could only confirm that the interface existed but was supported by Oracle.
I have not been able to find any documentation on installing this interface.
Can anyone supply directions or point me to someplace to look for them.
Any help you could give me would be greatly appreciated.
Ward

Hi all,
Ward - Brian is absolutely right. As I said in my first posting on this topic (above), we have
not yet developed an extension for JDeveloper to enable users to work with PVCS Version
Manager, which I believe is a specific product, rather than an interface.
This is why I'd greatly appreciate it if you could possibly provide more details of this Interface
and indeed what Oracle support for PVCS with JDeveloper Merant referred to. Please see my
first posting above for more details.
Brian - I'm sorry you do not agree with our approach of using the open published SCM Framework
to build your own extensions for using JDeveloper with other source code control tools than those
we support.
In an ideal world, we would have been able to offer support for every source code control tool on
the market with our first release of 9i JDeveloper. We were very keen to be able to achieve this and
we still plan and are currently looking into supporting more tools going forward and as many tools as
possible in the long term.
Unfortunately, we only have limited time available for each release and based on the feedback we
received, after our committment to support Oracle9i SCM, CVS and ClearCase were the most requested.
Therefore, we tried to reach a compromise to enable users to provide their own support for a specific
tool should they wish, if they did not use any of those tools supported. Indeed, our research suggests
that the market for source code control tools is quite fragmented and that customers use a wide range
ot tools. So, we decided to publish our own SCM Framework, the same one we used for the SCM, CVS
and ClearCase support, in order to help users build their own extensions in a similar way to ours.
Hope this helps,
Regards,
Dominic Battiston
JDeveloper Product Management
Oracle Corp

Database source code control or version management

Similar Messages

Maybe you are looking for