User profile for StephanieHerr

Hi Joseph, The early access release of SQL Source Control with Migrations v2 is now available. You can read more about this and download it from http://documentation.red-gate.com/displ ... ss+release. We do not have a command line yet, but should have that shortly (within a week or 2). I will update this forum as soon as it's available. This will help with automated deployments and pick up Migration scripts. It will then go into SQL Compare and SQL Data Compare (GUI and command lines), but I don't have an estimate for this yet. Regarding your requirements: 1) Migration scripts should work across the branches. Means, I need to deploy the database changes from Branch to database including migration scripts. This should work. We no longer rely on repository location or revision number so that Migrations will work across branches. 2) I need to include custom scripts for the deployment, this also should work in branch architecture. I don't understand how a custom script is different from a migration script that is used during deployment. Could you explain this more? 3) Both Migration scripts and Custom scripts need to deploy from one Branch to databases through the command line scripts As mentioned above, we should have a command line shortly that will pick up Migration scripts to be used in automated deployments. I'm not sure about what you mean by Custom scripts. Migration scripts are custom scripts that are re-used by SQL Compare during deployment. Cheers! / comments

Hi Joseph, The early access release of SQL Source Control with Migrations v2 is now available. You can read more about this and download it from http://documentation.red-gate.com/displ ... ss+rele...

0 votes

Hello. You can modify the CommandLineHooks.xml to do nothing in the commit. This will just save the files to your working folder. You'll need to add them to the changelist and commit using your own tool. You can also use the new link to "Working Folder" option. This option just scripts out the files and saves them to this folder from the commit tab. In SQL Source Control, the button on the commit tab is actually changed to say "Save." You would then use your own version control system's tool to add the files to the pending changelist and commit them. Strange that the powershell is not exiting. Cheers! Stephanie Herr [image] SQL Source Control Product Manager / comments

Hello. You can modify the CommandLineHooks.xml to do nothing in the commit. This will just save the files to your working folder. You'll need to add them to the changelist and commit using your o...

0 votes

This process can cause issues if a developer by accident checks in the development version of the synonym by accident if the checkmark is not deselected during the checkin process to SVN. Have you tried using SQL Source Control's filter feature so that synonyms don't accidentally get checked into SVN? Right click on the db in the Object Explorer and then select Other SQL Source Control tasks > Edit filter rules... Then, uncheck synonyms on the left and save and close. Now, the synonyms should not show up on the commit list anymore so developers don't have to remember to deselect them every time they commit. Make sure you commit the filter configuration so other developers stop seeing the synonyms on their commit lists too. I hope this helps! / comments

This process can cause issues if a developer by accident checks in the development version of the synonym by accident if the checkmark is not deselected during the checkin process to SVN. Have...

0 votes

If possible, I would recommend using the dedicated database model. Therefore, each developer would have their own copy of the database and their changes will NOT impact anyone else until the other users explicitly decide to Get Latest. Other users can see exactly what changes have been made before they update their copy. With or without SQL Source Control, you will always have this problem of overwritting another developer's changes if multiple developers are working against the same db. In a dedicated model, if 2 developers work on the same object, the first one to commit will have no problems. The second developer will see a conflict when they try to commit. They can decide to take the changes in source control and then they may need to reapply the changes that they made. Or, they can decide to keep their changes and reapply the other devs' changes. (For complex changes, I would recommend using a seperate merge tool to merge the 2 scripts.) I'd love to hear more about your evaluation and anything that would prevent you from going to a dedicated model. If you have to work on a shared model, then hopefully this will be rare when it could cause a problem like you say. All users should see blue indicators on the Object Explorer, which indicates changes which have not been committed yet. This is not the same as locking an object so other users can not edit it, but it could be a good warning that someone else currently has edits to that object, so I better wait till they're finished. Currently, we have not implemented an exclusive checkout feature. You may want to vote comment on this feature request at https://redgate.uservoice.com/forums/39 ... ?ref=title. I just had a quick chat w/ David... Unfortunately, linking to a working folder independent of TFS still won't help stop multiple users in the same database from overwriting each others' changes. / comments

If possible, I would recommend using the dedicated database model. Therefore, each developer would have their own copy of the database and their changes will NOT impact anyone else until the other...

0 votes

See the following post for details: http://www.red-gate.com/MessageBoard/vi ... 9441#49441 / comments

See the following post for details:http://www.red-gate.com/MessageBoard/vi ... 9441#49441

0 votes

The 2.2 Release Candidate will be available later today. We will post an update as soon as it is available. Thanks! / comments

The 2.2 Release Candidate will be available later today. We will post an update as soon as it is available. Thanks!

0 votes

Hi Jason, You shouldn't upgrade to 2.0. Please continue to use the Git EAP for now. v2.0 is only for SVN/TFS users and does not include Git. We hope to have Git in v2.1 in the next month or so. Check the box that says "Don't tell me about this version again" so that you stop getting the notifications for v2.0. You will get the next notification when v2.1 is released. / comments

Hi Jason, You shouldn't upgrade to 2.0. Please continue to use the Git EAP for now. v2.0 is only for SVN/TFS users and does not include Git. We hope to have Git in v2.1 in the next month or so. ...

0 votes

Thank you for letting us know that this page is out of date. We are working to update it now. In the meantime, you can download our Toolbelt Installer, which contains SQL Source Control v2.0 and the SSMS Integration Pack from http://www.red-gate.com/products/sql-de ... l/download Thanks again! / comments

Thank you for letting us know that this page is out of date. We are working to update it now. In the meantime, you can download our Toolbelt Installer, which contains SQL Source Control v2.0 and t...

0 votes

Hello, v2.0 is only for SVN/TFS users. Please ignore this update for now. v2.1 will have the full support for Vault and Vault Pro. We expect that at the end of March or early April. For now, please uninstall using your Control Panel and reinstall the Vault Beta, which is available at http://downloads.red-gate.com/EAP/SQLSo ... EA_VVG.zip. / comments

Hello, v2.0 is only for SVN/TFS users. Please ignore this update for now. v2.1 will have the full support for Vault and Vault Pro. We expect that at the end of March or early April. For now, ple...

0 votes

You may want to vote/comment on the specific suggestion at http://redgate.uservoice.com/forums/390 ... se-project / comments

You may want to vote/comment on the specific suggestion at http://redgate.uservoice.com/forums/390 ... se-project

0 votes

How can we help you today?

StephanieHerr

Comments