Multiple Projects in TFS, one schema in Oracle database

Toad for Oracle & DevOps Toolkit
1

Hi!

I would like to use TFS (2013) as VCS in combination with team coding (TOAD 12.8) and have a question:

We need to maintain serveral database objects in different TFS projects but they will be all in the same database schema. (They extend existing objects with more specific information.) I have not been able to set up more than one team project which connects to this schema. The objects itself would be separated by a prefix as namespace and filtering by “filters” would be possible. Any help? Is it possible at all?

Thanks in advance w/regards

Thorsten

2

Hi Thorsten,

Unfortunately, you cannot split a schema across multiple VCS projects in Team Coding. We used to have that ability in older versions and found it created chaos when trying to resolve database objects to their respective code collection groups. As a result, this was simplified in Toad 12.7 and higher so that a Team Project (and database schema) was tied to a single root VCS project.

There is additional flexibility with controlling VCS folder organization in the Toad 12.9 beta, though. For example, let’s say you have the following VCS structure:

$/

$/Project1

$/Project1/Application1

$/Project1/Application1/Programmability

$/Project1/Application1/Programmability/Schema1

$/Project1/Application1/Programmability/Schema2

$/Project1/Application1/Tables

$/Project1/Application1/Tables/Schema1

$/Project1/Application1/Tables/Schema2

$/Project1/Application1/Views

$/Project1/Application1/Views/Schema1

$/Project1/Application1/Views/Schema2

$/Project2

In Toad 12.9 beta, you can set up a Team Project and specify “$/Project1” as your VCS Project, tell it to use subfolders, set “Application1” as your parent folder, and choose the option to organize your objects by “Object Type / Schema / ”. You can then further customize the object type folder names such that Procedures, Functions, and Packages all resolve to “Programmability” and tables and views resolve their own folder names. All the database objects will still need to exist within the same VCS project for the schema, but you will have additional room to customize the folders to your needs.

-John

From: thorsten.herrmann [mailto:bounce-thorstenherrmann@toadworld.com]

Sent: Thursday, March 17, 2016 4:58 AM

To: toadoracle@toadworld.com

Subject: [Toad for Oracle - Discussion Forum] Multiple Projects in TFS, one schema in Oracle database

Multiple Projects in TFS, one schema in Oracle database

Thread created by thorsten.herrmann

Hi!

I would like to use TFS (2013) as VCS in combination with team coding (TOAD 12.8) and have a question:

We need to maintain serveral database objects in different TFS projects but they will be all in the same database schema. (They extend existing objects with more specific information.) I have not been able to set up more than one team project which connects to this schema. The objects itself would be separated by a prefix as namespace and filtering by “filters” would be possible. Any help? Is it possible at all?

Thanks in advance w/regards

Thorsten

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - General notifications altogether.

Toad for Oracle - Discussion Forum

Flag
this post as spam/abuse.

3

Hi John

thanks for the quick answer. Unfortunately this feature doesn’t solve my problem. We have a generic framework since 15 years and more than 60 projects which contribute their own extensions to it. Which makes perfectly sense because each project extends it’s own concern and (usually) is not related to the other projects. And further more this projects do consist of more than one technology. Therefore our way of version control is project and not technology centric:

/project 1

/database

/tables

/views

/etc

/technology 1

/technology 2

/technology 3

Is it possible to automate TOAD to format code, check code metrics, etc by command line? These are the services I would have liked to use during check in.

Regards,

Thorsten