Quick overview of how to install GitHub and then interact with it directly through the SQL Navigator tool via the Team Coding feature.


So let’s get started!  Following is a list of all of the tools that you may need to Download and Install to complete configuration of SQL Navigator Team Coding with Version Control provided by Git/GitHub

  • Install GitHub Desktop (Its Git but for the server).  You might have to create an account, go for it, it’s ok, try something new!
  • Download and install GitHub command line client (be sure to select the ‘Windows command line’ option)
  • Install SQL Navigator

With those apps downloaded and ready to install, here’s a summary of what we’re going to do:

  1. Install and configure GitHub command line
  2. Install and configure GitHub Desktop
  3. Install SQL Navigator
  4. Configure SQL Navigator Team Coding to connect to GitHub Repository
  5. Configure SQL Navigator Team Coding to ignore certain objects by type and name
  6. Check out a schema object, alter it, check that change back into version control and observe updates

…and here are the detailed steps…

Install GitHub Command Line and be sure to choose the following two non default options when given the chance (all other pages choose the defaults):



Launch GitHub Desktop and create a repository, I’ll call mine ‘SQLNavRepo’ (the local path is up to you, I just used the default because I don’t like to make things more complicated than they need to be)


With repository ‘SQLNavRepo’ selected in the left-hand side, create a new Branch (this is your own private sandbox version of the repository where you can make mistakes and experiment before committing changes from your branch into the main branch)


In SQL Navigator – Connect to the repo you just created


In SQL Navigator, select Team Coding | Administer | Team Projects | Right Click | Create a new Team Project…


Name the project then click the ellipsis (…) then ‘New…’


Name the project then OK


Select the newly created project and then click OK 


Now specify the objects to be controlled.  Here we can either choose by object type (Tables, Views, Procs) or by wildcard text name filter which objects to place under control of the new project.

Click the ‘New’ icon…


Choose the schema you want to manage and click OK


By default all schema objects regardless of name are to be added to the Team Project.  You can uncheck schema objects or click the ellipse (…) to filter by regex terms.


All Done, click OK to continue:


Depending on the number of DB Objects you’ve chosen to manage via Team Coding, you may need to wait a tic or two for the creation of the project to complete, but when you’re done just click OK to dismiss the previous dialog, then from the SQL Nav menu, select Team Coding | Team Coding Manager to confirm that the expected objects were added to your new team project (The big green checkmark tells me everything worked):


Now, we can finally start using Team Coding.  If you are developer, the first thing you’ll want to do is check out some procedural code and start working.  So it’s simple, just Right click controlled objects to Check-out (or later Check-in, Get latest version, Compare contents, etc.)


Now I’m asked to log into my Git account – do that and click OK


Now add a comment (optional), confirm objects to be checked out, and then click OK…


Visual cue in SQL Navigator that the procedure is now checked out:


Launch Github, I can see the same information…stored proc HR.ADD_JOB_HISTORY is checked out:


Now open the stored proc in SQL Nav editor and make some changes, then save


Satisfied with the changes (maybe do some unit testing, code quality checks), return to the Team Coding Manager, right click and select Compare contents.


Confirm that your local file is different than the Version controlled one…


And if you’re like me, sometimes I’d like to double check by making sure that GitHub sees the same change…it does…


Finally, back to the SQL Navigator Team Coding manager to check the new change in.  Just right click on the stored proc and choose ‘Check in’


Add your comment and click OK


And that’s all there is to it.  To learn more check out the SQL Navigator user community.


About the Author

Brad Wulf

Brad Wulf has held in numerous roles over the past 15 years within the Database world including Technical Support, Build Management, Development and Presales.

Notable Replies

  1. says:

    Hi, Thanks for the insightful post.
    We are setting up git repository and intend to leverage Team coding for Oracle DB objects development work while having a version control in place.

    As I understand, we need to first create a project under Team coding and then select all objects that we want to be enabled for version control or in other words all the objects being used in our client project.

    There are hundreds of objects used in our project, so we need to select all of them for 2 reasons:
    a. this will export DB objects as files in the local git repository path setting up the local repository. These files needs to be pushed to remote git repository so that initial repository set up is completed.
    b. Going forward, for any development activities on DB objects since all the objects are enabled as team coding objects (TCX tables) all the developers can work directly under same project created initially from the Team Coding Manager without accessing the actual objects in DB.

    a. To work with Team coding and for the initial git repository setup, is this the right way of doing it. i.e. Option 1: selecting all relevant objects when setting up Team coding projects so that file gets exported in local repository. If not, what could be the alternative way? Option 2: maybe, to export files outside of team coding manager to setup git repository and then create team coding project for each development cycle wherein we just mark only those objects that indeed needs to be modified?
    b. Will Option 1 cause any performance issue using Team Coding?
    c. When should we create projects in Team Coding? for option 1, I will have just one project, can all developers work on the same project? for option 2, is there any drawback of having n number of projects. what is the right way to use Team coding?

    Any insight will be much appreciated. Thanks!