How to organise a VSTS Database Edition Solution/Project (GDR)?

Question

We use TFS and are looking at using VSTS Database Edition GDR . I would like to know the best way to structure our projects and wondered if anyone has any experience in this.

Let me explain our environment.

We have 3 environments, DEV , TST and PROD.

Each of these have multiple databases.

Currently, we have solution file(s) for each logical group (Cluster, Readonly1 , Readonly2, Reporting) with a project for each database in each group. We then have configurations for each environment.

In the new world of the GDR, we want to utilise the partial project features so we dont have to duplicate schema changes if objects are identical across projects and also we want to create a "Server" (or multiple?) server projects for dealing with permissions, logins , jobs etc.

Does anyone know of good way to structure the solution(s), project(s) in this scenario?

Answer 1

You might want to edit your question. I believe by saying 'GDR' you mean the VSTS Database Edition GDR which adds new features to the Database tools.

I haven't spent much time using the VSTS Database Edition, but this sounds to me more like a source branching / forking question than a question of how to layout your project.

Answer 2

We have seen some odd behavior that it deploys when we just wants it to create new scripts so be careful...

Latest bugs in the product seems to be published on the team blog http://blogs.msdn.com/vstsdb/default.aspx

Answer 3

I hate to day it but I would suggest a trial project to see which works best for you. I have seen no best practice as yet.

Remember that the the various projects whether the are C# or DB ones can be assembled into any group using solutions. I am find more and more that the solutions I use as a developer has less to go with the underling project structure and more what I need to do on any given day.

I would suggest you look at building you project using an automated build system, and this could be the biggest factor in how you split it into partial projects.