Integration with Source Control

• 
  SQL Compare 6 doesn't interact with source control systems. It merely saves files in a format that can be bound to source control, but this is a step you must take using your source control client.
  
  Some editors will let you check in/out files and folders from source control so this will work for you if you are modifying the SQL scripts offline. However if you are synching back from a live database to scripts on your hard disk, you will need to check these in to source control as a separate step.
  
  David Atkinson
  Red Gate Software

  David Atkinson May 16, 2007 09:05

  - 0 +
• 
  David,
  
  If I understand correctly, before I synchronize a database to my script files that are under source control, I need to check out all files that could be affected. Is this the case? If so, I view this as a huge shortfall. The whole point of managing script files is to facilitate source control. To expect developers to check out all script files before a compare is done simply isn't feasible.
  
  Randy
  
  

  David Atkinson wrote:

  SQL Compare 6 doesn't interact with source control systems. It merely saves files in a format that can be bound to source control, but this is a step you must take using your source control client.
  
  Some editors will let you check in/out files and folders from source control so this will work for you if you are modifying the SQL scripts offline. However if you are synching back from a live database to scripts on your hard disk, you will need to check these in to source control as a separate step.
  
  David Atkinson
  Red Gate Software

  randyminder May 16, 2007 09:31

  - 0 +
• 
  Randy,
  
  Going forward we definitely have plans to implement proper SCC integration, but for the initial v6.0 release, objects will need to be checked out manually.
  
  You will be able to compare from scripts to a live DB without doing a check out. But when you synch from a live database to scripts, any object scripts that will be modified should be checked out.
  
  Can you expand on precisely what sort of source control integration you are expecting in SQL Compare? At what stage of the process do you think it should check out the relevant object scripts?
  
  Thanks for the feedback,
  
  David Atkinson
  Red Gate Software

  David Atkinson May 16, 2007 10:30

  - 0 +
• 
  David,
  
  What I would be expecting would be the same level of integration that Visual Studio DB Pro has. When I compare a database to a project, and I choose to update the project based on the comparison, DB Pro checks out all script files as necessary. We're a 10 developer team working with a schema containing 3500 objects. It's just not practical to expect each developer to check out all 3500 objects (files) when synchronizing to the script files. And, it would be far too time consuming to selectively check files out, especially if the number of files more than a dozen or so, which I think would happen frequently.
  
  Randy
  
  

  David Atkinson wrote:

  Randy,
  
  Going forward we definitely have plans to implement proper SCC integration, but for the initial v6.0 release, objects will need to be checked out manually.
  
  You will be able to compare from scripts to a live DB without doing a check out. But when you synch from a live database to scripts, any object scripts that will be modified should be checked out.
  
  Can you expand on precisely what sort of source control integration you are expecting in SQL Compare? At what stage of the process do you think it should check out the relevant object scripts?
  
  Thanks for the feedback,
  
  David Atkinson
  Red Gate Software

  randyminder May 16, 2007 11:09

  - 0 +
• 
  I see where you're coming from. We'll look into improving this going forward.
  
  What does DBPro do when a file that it needs to check out is checked out or has been since modified by another user?
  
  David Atkinson
  Red Gate Software

  David Atkinson May 16, 2007 13:09

  - 0 +
• 
  The scenario you describe isn't really a DBPro of SQL Compare issue. If DBPro (or any process) attempts to check out a file that is already checked out, an error will occur from the source control system, unless multiple checkouts are turned on. If multiple checkouts are turned on and another user has modified the file, this is a source control merge issue.
  
  Randy
  
  

  David Atkinson wrote:

  I see where you're coming from. We'll look into improving this going forward.
  
  What does DBPro do when a file that it needs to check out is checked out or has been since modified by another user?
  
  David Atkinson
  Red Gate Software

  randyminder May 16, 2007 13:36

  - 0 +

Add comment

Please sign in to leave a comment.