Skip to content

Settings and activity

5 results found

  1. 27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment

    Can I ask what version of SQL Source Control you are on?

    We made significant improvements to list generation performance in v3.0.9.18.

    Further improvements in performance when Data is linked will follow in a subsequent release next week.

  2. 476 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    64 comments  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    under review  ·  Kendra responded

    Thank you everyone for the suggestions and votes for this over the years.

    I’d like to surface up a workaround for the “linking” problem which is mentioned in the comments. For the use case of easing pains around environment setup with a large number of databases, we have had customers find success using code based off Alessandro Alpi’s blog post: https://alessandroalpi.blog/2016/06/28/automatically-link-databases-to-red-gate-sql-source-control/

    I do understand that this is a broader issue and hear that many of you also want command line or API support for the product in general.

    If there are specific scenarios or workflows that would be useful to automate for you, this feedback is also very useful, and if you have details on the type of VCS you use and the workflow (such as a branching model) that it would fit in to, that would be very helpful for us to hear as well.

    An error occurred while saving the comment

    Following changes made in SQL Source Control version 3.0.9.18, you can now pass around a config file to help get additional users linked to nemerous databases more quickly. This release is currently available via the Check For Updates option from the application's Help menu.

    Disclaimer: This is clearly not a proper solution for this suggestion (we are planning to work on that in a future version of the product), but it might help you get other users set-up with fewer manual steps!

    So, here it goes:

    1. Setup SQL Source Control on one machine with all the linked databases that are required. Then copy the following file from that machine:
    C:\Users\[username]\AppData\Local\Red Gate\SQL Source Control 3\LinkedDatabases.xml

    2. This file should be placed into the same location (C:\Users\[username]\AppData\Local\Red Gate\SQL Source Control 3) on other machines where you would like these databases to be linked ([username] in this path should be the user who will be using the copied configuration on this machine).

    3. So, when the new user connects with SSMS to the server where the linked databases reside, they should see green database nodes in the object explorer indicating databases linked to source control. However, when one of these nodes is selected, because SQL Source Control has not got a local working copy of the database schema, it will prompt the user with the following question and they should reply YES to this:
    "There are no local files fore the database [database name]. Would you like to link it to source control?"

    4. SQL Source Control will then create the local files it needs to work with the database and the user should be up & running.

    It is worth noting that at the moment this does not work with Migration Folder locations (they cannot be copied in the above way).

    Cheers,
    Chris

  3. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment

    It sounds like you're using the "For specific changes" option when creating a migration script and selecting a couple of different revisions by selecting with the CTRL key pressed. When you generate your script, is your issue that it still includes the changes the unselected scripts contained?

    If so, this is normal - it's more a case of the interface not correctly stopping you doing it (i.e. it should ideally force you to select a contiguous set of changes).

    Creating a migration script for non-contiguous changes is not possible, because there could be all sorts of dependent changes in the interim revisions that you didn't select that you would then be excluding. When you pick two revisions by holding down CTRL, you could think of it more as "create a script from "this" revision to "that" revision.

    In your workflow, I think you'd need to create two migration scripts - one for each revision you want to replace.

  4. 11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  SQL Compare  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment

    The filter should be passed from SQL Source Control to SQL Compare - this was added in SQL Compare v10 and SQL Source Control v2.2.

    You should be able to see your SQL Source Control filter in the dropdown list of filters in the top left-hand corner of the Comparison Results screen in SQL Compare.

    Please let us know if this doesn't do what you'd expect or if you need any more help with filters.

  5. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment

    At the moment we recommend using SQL Source Control with a local db and then deploying to SQL Azure with SQL Compare. This avoids latency when making schema changes to your development database.