Hi Perry,
I'd strongly suggest normal backup would be a better strategy for those items.

Source Control is really designed for those things that you use to build a 
system. Code, parameters, schema (file & dictionary) generation scripts, etc.  
The data for that system would typically *not* be kept in source control 
(unless you're feeling masochistic ;).

Just in case you haven't seen this: http://tfsguide.codeplex.com/ has 
guidelines for what you want to do and which is TFS specific.

Also, from what I just read, TFS is not case sensitive which will be an issue 
if you ever have 2 items under control with differently cased equivalent names. 
Payroll.Rpt & PAYROLL.RPT

-----Original Message-----
From: u2-users-boun...@listserver.u2ug.org 
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Perry Taylor
Sent: Wednesday, 24 August 2011 10:50
To: 'u2-users@listserver.u2ug.org'
Subject: Re: [U2] [UV] Microsoft Team Foundation Server for Source Control

Not source but code lists which are updated at different intervals.  Some 
examples: ZIP, CPT, ICD9, etc.


----- Original Message -----
From: Boydell, Stuart [mailto:stuart.boyd...@spotless.com.au]
Sent: Tuesday, August 23, 2011 07:49 PM
To: U2 Users List <u2-users@listserver.u2ug.org>
Subject: Re: [U2] [UV] Microsoft Team Foundation Server for Source Control

What "source" are you keeping that has 2.5 million records????

-----Original Message-----
From: u2-users-boun...@listserver.u2ug.org 
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Perry Taylor
Sent: Wednesday, 24 August 2011 01:39
To: U2 Users List
Subject: Re: [U2] [UV] Microsoft Team Foundation Server for Source Control

Thanks to everyone for some very interesting points.  I am particularly 
intrigued by Stuart's handling of dictionaries using triggers.  One particular 
challenge I may face is one particular hashed file (not a dictionary) which 
contains 2 1/2 million records that are under source control today.  Copying 
them out to a directory might pose some problems with inode consumption.

Perry


_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for 
the sole use of the intended recipient(s) and may contain confidential and 
privileged information.  Any unauthorized review, use, disclosure or 
distribution is prohibited. ZirMed, Inc. has strict policies regarding the 
content of e-mail communications, specifically Protected Health Information, 
any communications containing such material will be returned to the originating 
party with such advisement noted. If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message.
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users



_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to