SQL Server Data Tools

Play SQL Server Data Tools

The Discussion

  • User profile image
    AnthonyJS

    Some very nice features in this tool.

    It would be really great for more sessions to be done on versioning and publishing, and if possible scripting this as part of a build.

  • User profile image
    compupc1

    This is a nice overview!

    We use database projects to manage our database schema for our Azure-based SaaS application.  Our app is growing and we will soon need to shard.  With the new sharding strategy (replacing federations), I wonder if the SSDT can be used to manage schemas across many databases.  Is it possible to publish a schema change to a group of databases?  I'm sure there are some challenges around this, but it would seem to be that some measures could be taken to keep things consistent -- e.g. validating as much of the schema change up-front against all shardlets before actually publishing the changes to each.

    SSDT is such a fantastic way of managing our schema within our SDLC.  It would be a real shame to have to manage this stuff manually once we begin sharding.

  • User profile image
    SQLScott

    Hi compupc1, currently SSDT does not handle publishing to multiple databases, but I will certainly take this back to the team. Thank you for the input, fantastic idea!

  • User profile image
    MattYet​AnotherUser​Name

    Why don't you have someone present who understands the product, and has researched what it can do and how rather than just relying on out-dated knowledge.

    Saying "oh, I didn't know it could do that" is just the same as those devs who you were criticizing at the beginning for now knowing it was there at all because they were used to other tools such as SQL Server management studio.

  • User profile image
    jim

    Thanks for the show. Tried some of the sql stuff from visual studio a few years ago and it was very lacking - thanks for the reminder - just tried it in VS2013 Community edition and it does what I need - funny - you can COPY a column name in the SERVER EXPLORER window but it doesn't paste or drag to editor window. Also may help to show the different versions and how they look cause mine says SERVER EXPLORER on the toolbar heading.

  • User profile image
    compupc1

    Thanks @SQLScott!  I really think having great tooling for SQL Azure's new Elastic Scale will be important for its success -- and personally I think SSDT makes sense as one of the ways to deliver this, especially for those of us who can't/don't use EF migrations; why create yet another schema management workflow!  SSDT = good stuff.

  • User profile image
    JStellato

    , AnthonyJS wrote

    Some very nice features in this tool.

    It would be really great for more sessions to be done on versioning and publishing, and if possible scripting this as part of a build.

     

    I agree, I only work on small business applications, but it would be great to see how teams handle versioning and publishing as well. 

  • User profile image
    Osco

    Nice! Visual Studio is the best IDE that exists today.

  • User profile image
    vikas

    I am using SSDT for delivering the database build from QA to many different environment, below is my observation while comparing database.
    1. This Data tools should have option to validate the column order. Like we should have one option where we can check or uncheck that column order will matter or not for source and target.
    2. This tools shows differences when your primary key name are different, even though you have same primary key column. It should have option to check the primary key name differences so a user can decide either I have to compare the name of the constraint or only the constraint columns. Same problem we have with other constraints.
    3. When we have extra column in target and tool generating the script to drop the column, and this column is used in some indexes then tools should give script to drop the index first and then drop the column, but it’s not happening.
    4. When a column is changed to not null from the null or adding new column with the NOT Null then this tool should generate the alert that this will fail or it should be add default values for the column. But it’s not happening, the script generated by data tool is getting fails.

  • User profile image
    SQLScott

    Great feedback AnthonyJ and JStellato. We'll focus our next video on versioning and deployment.

  • User profile image
    Amerisun

    I know this episode was a while back, but I was able to watch this episode just now, due to being completely disconnected during the Christmas break and playing too many games. ;)  I would love to see some examples of versioning and deployment, how you would say take a pre-existing database and create a "version 1.0" project from that (Schema and Data?), then enact changes to it.. then how to deploy those properly through a database project in VS using these tools.  That would be most excellent.


    Thanks for the great content as always Robert (and thanks Scott for this episode!)!

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.