Geek Answers Handbook

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

We use TFS and are considering using the GDR VSTS Database Edition. I would like to know how to best structure our projects, and I wondered if anyone had any experience with this.

Let me explain our environment.

We have 3 environments, DEV, TST and PROD.

Each of them has several databases.

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

In the new GDR world, we want to use the partial functions of the project, so we do not need to duplicate the changes in the scheme if the objects are the same for all projects, and we also want to create server projects (servers) (or several?) To allow permissions, logins, workstations and etc.

Does anyone know a good way to structure the solutions (s) projects in this scenario?

+5
source share
3 answers

You might want to change your question. I believe that by saying "GDR" you mean the GST VSTS Database Edition, which adds new features to the database tools.

VSTS Database Edition, / , , .

+1

, , , . .

, , # DB, . , , , underling , .

, , , , .

+1

We saw the odd behavior that it expands when we just want it to create new scripts so be careful ...

Recent product bugs seem to be posted on the team blog http://blogs.msdn.com/vstsdb/default.aspx

0
source

More articles:


All Articles