Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

TFS Solution Structure Best Practice? Expand / Collapse
Author
Message
Posted Tuesday, May 20, 2014 2:45 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 8:13 AM
Points: 62, Visits: 175
Hi,

I'm fighting my way through putting a dozen databases into TFS and am trying to figure out what the most serviceable structure would be.

Here's what I've got:

SQL Server 2005
VS 2012 (you can see where the priorities are!)

I've created: 1 Team Project but I'm wondering how to structure the dbs into 'solution(s)'

We have 3 DBs that comprise production (and production ETL), 2 DBs that make up our Test set and 2 DBs that make up our Dev set.

Has anyone done this long enough to have a recommendation on whether to put all dbs in one solution or to break them out by function--I'm thinking that perms on the solutions might be nice, e.g. don't let just any schmoe have access to the Prod solution.

Thanks for your feedback and if you have time, please share any info that was a stumbling block for you!

Post #1572913
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse