Wishes for ReadyRoll

vrafaelvrafael Posts: 3
edited November 28, 2016 11:20PM in ReadyRoll
Hello!

I like ReadyRoll and I have some wishes for RR team (sorry for my english)
1. Hubrid approach
Deployment Order issues
Uncomfortable listbox for programmable objects deployment order in project settings
Would like auto sorting programmable objects for deployment. I offer use target database dependencies hierarchy for sorting
2. Migration-based approach
If two developers altering procedure or function in isolated branches then after merge migration win last change
3. ExcludeObjectsFromImport
Interface for exclude objects in project properties
4. SHADOW Database
Create shadow database on localdb with target database collation! Deployment script with '??????????' in default value for varchar columns when DB collation is differ

Thank you for your job!

BestRegards
Rafael Valiullin

Comments

  • Hi Rafael,

    Thanks very much for providing that great feedback.

    Regarding your first suggestion, you can vote for this feature to be implemented here:
    https://readyroll.uservoice.com/forums/ ... s-by-their

    Regarding your second suggestion, we currently recommend that programmable objects are used to avoid this kind of scenario with code-based objects. Was there a particular scenario you had in mind where usage of migrations-only was imperative or where programmable objects were unsuitable?

    Regarding your third suggestion, you can vote for this feature to be implemented here:
    https://readyroll.uservoice.com/forums/ ... ns-to-be-s

    Regarding your fourth suggestion, you can vote for this feature to be implemented here:
    https://readyroll.uservoice.com/forums/ ... into-proje

    You can resolve the collation issue by including the collate clause in your "Pre-Deployment1_CreateDatabase.sql", e.g.
    	CREATE DATABASE [$(DatabaseName)] COLLATE SQL_Latin1_General_CP1_CS_AS;
    
    You will then need to drop the Shadow db from the (localdb) instance, and close/re-open your ReadyRoll project.

    Also, if you intend to deploy your target database from scratch on (localdb) then you may want to add this to your sqlproj file:
    <PropertyGroup>
        <DefaultCollation>SQL_Latin1_General_CP1_CS_AS</DefaultCollation>
    </PropertyGroup>
    
    This will ensure that SSDT (upon which ReadyRoll is based) automatically creates an empty DB with the correct collation. Please let me know how you go with this.
    Daniel Nolan
    Product Manager, ReadyRoll
    Redgate Software
  • Thanks for your reply Daniel!

    Now I use hybrid approach, it's most suitable for me.
    And I included the collate clause in pre-deployment script - collation differ problem has solved!
  • That's great Rafael.

    And thanks very much for all the recent feedback on uservoice!
    Daniel Nolan
    Product Manager, ReadyRoll
    Redgate Software
Sign In or Register to comment.