How can we help you today? How can we help you today?
adam_hafner
@Jon_Kirkwood I just updated to 4.1.21 and it's still throwing the same error message for coverage in SQL Test.  Can you escalate to your team to investigate?  Thanks! / comments
@Jon_Kirkwood I just updated to 4.1.21 and it's still throwing the same error message for coverage in SQL Test.  Can you escalate to your team to investigate?  Thanks!
0 votes
@Morris, We use TFS + SOC where I work and it is very helpful.  It streamlines the tedious tasks of generating and checking in objects.  It also helps in identifying objects that have changed.  One thing that I would strongly suggest is using the 'Dedicated' model for source control.  The 'shared' model seems simple, but it really only works well with very few developers or if code is handled in silos between developers (ie Bob only changes certain tables/procs, Erin only works on other certain tables/procs, and neither Bob or Erin work on the same stuff at the same time).  Dedicated does mean you have to figure out how to provide your developers with SQL Server instances, either locally on the developer workstations or somewhere else (server, cloud, etc), but you can generally get that figured out with the Developer Edition of SQL Server for local installs.  It's worth it in the long run by not having to worry about people changing the same objects at the same time with different changes.  You will really want to understanding branching/merging/conflict resolution as that is a somewhat difficult task, but I can't say if it is better or worse than without SOC.  Either way they happen, it just depends on how you coordinate the communication within your team to resolve the changes. / comments
@Morris, We use TFS + SOC where I work and it is very helpful.  It streamlines the tedious tasks of generating and checking in objects.  It also helps in identifying objects that have changed.  One...
0 votes