Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Recommendations for TFS organization structure for DBAs only


Recommendations for TFS organization structure for DBAs only

Author
Message
jasonclements32304
jasonclements32304
SSC Rookie
SSC Rookie (28 reputation)SSC Rookie (28 reputation)SSC Rookie (28 reputation)SSC Rookie (28 reputation)SSC Rookie (28 reputation)SSC Rookie (28 reputation)SSC Rookie (28 reputation)SSC Rookie (28 reputation)

Group: General Forum Members
Points: 28 Visits: 201
Sorry for the misuse of terms. I'm new to source control.
Does anyone have recommendations for TFS organization structure for DBAs only?

Should our source folder pathing be?
$\DBA\username?

$\DBA\Servername\Database_name?

$\DBA\Servername\Database_name\Project?

We thought we try the TFS because we have MSDN subscriptions and have a enough licenses to support the DBA team.

We have 500+ SQL servers and 50-100 DBs on each server. We were thinking many of the DBs are third party and we wouldn't need to source control those DBs. But any DBs we do customization or are built and maintenance by us we would want it in TFS server correct?


Rick Krueger
Rick Krueger
SSC Veteran
SSC Veteran (262 reputation)SSC Veteran (262 reputation)SSC Veteran (262 reputation)SSC Veteran (262 reputation)SSC Veteran (262 reputation)SSC Veteran (262 reputation)SSC Veteran (262 reputation)SSC Veteran (262 reputation)

Group: General Forum Members
Points: 262 Visits: 691
My advice would be to look at TFS no differently than a share out on a file server. Think about each database as a folder. Its subfolders will be tables, stored procedures, views, etc. Then, think about how you would logically organize those folders on your file server. The one caveat is that moving folders around in TFS won't be as easy as moving folders around on a share. So, just get that structure figured out before you start putting things into TFS. DBPro's schema compare should make it relatively easy to pull the structure into a Database Project, and get it into TFS.

So, if your databases are unlikely to change servers, I like:
$\DBA\Servername\DatabaseName or $\DBA\Servername\Department\DatabaseName

And yes, one of the advantages of TFS is having history of who changed what when, so no real value in adding 3rd party databases.



Rick Krueger

Follow @dataogre
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search