Visual Studio Tools

  • Comments posted to this topic are about the item Visual Studio Tools

  • I had no idea about the answer, I guessed it and got it right. 🙂

    Off late, there are so many questions on Visual Studio tools in QotD section.

    It would be great if someone could share names of books on this topic for beginners.

    M&M

  • Had to resort to Google on this one since I didn't have a clue.

    Please see Microsoft MSDN for further info.

  • Nice question. And thanks Chris for posting the reference.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • I'm loving the reference to "Visual Studio Database Davelopment Tools"... that's how I shall think of it henceforth 🙂

    Dave.

  • dave.farmer (3/10/2011)


    I'm loving the reference to "Visual Studio Database Davelopment Tools"... that's how I shall think of it henceforth 🙂

    Dave.

    Ha ha. Whoops, my bad!

  • mohammed moinudheen (3/9/2011)


    I had no idea about the answer, I guessed it and got it right. 🙂

    Off late, there are so many questions on Visual Studio tools in QotD section.

    It would be great if someone could share names of books on this topic for beginners.

    I second this. Until recently, the database tools were not part of our company's MSDN subscription so I never got a chance to use them and have just learnt to live without them. So do you know of any introductory article we could read - along the lines of "Visual Studio 2010 Database Development Tools and What They Can Do For You"? If not, perhaps you might consider writing one yourself? 😉

    Thanks,

    Duncan

  • Duncan Pryde (3/10/2011)


    mohammed moinudheen (3/9/2011)


    I had no idea about the answer, I guessed it and got it right. 🙂

    Off late, there are so many questions on Visual Studio tools in QotD section.

    It would be great if someone could share names of books on this topic for beginners.

    I second this. Until recently, the database tools were not part of our company's MSDN subscription so I never got a chance to use them and have just learnt to live without them. So do you know of any introductory article we could read - along the lines of "Visual Studio 2010 Database Development Tools and What They Can Do For You"? If not, perhaps you might consider writing one yourself? 😉

    Thanks,

    Duncan

    Duncan,

    I previously posted some links here: http://www.sqlservercentral.com/Forums/Topic1065433-200-2.aspx that may or may not be useful!

  • This one may be particularly useful: Visual Studio 2010 SQL Server Database Projects

  • Jamie Thomson (3/10/2011)


    This one may be particularly useful: Visual Studio 2010 SQL Server Database Projects

    Thanks for the links - I discovered after I posted that you have a number of entries on your blog as well which look interesting.

    I think what I'm after is some idea as to why I should start using "Datadude" if I've never used it before. I'll have a look through the various articles and see what I can find though.

    Thanks,

    Duncan

  • Jamie Thomson (3/10/2011)


    This one may be particularly useful: Visual Studio 2010 SQL Server Database Projects

    Thanks for the references!

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Duncan Pryde (3/10/2011)


    Jamie Thomson (3/10/2011)


    This one may be particularly useful: Visual Studio 2010 SQL Server Database Projects

    Thanks for the links - I discovered after I posted that you have a number of entries on your blog as well which look interesting.

    I think what I'm after is some idea as to why I should start using "Datadude" if I've never used it before. I'll have a look through the various articles and see what I can find though.

    Thanks,

    Duncan

    yeah, that's a hard one to articulate. For me, I reached a point where it just "clicked" and I don't think that can happen until you use the product.

    The big benefits as far as I can see them are:

    -Development-time error checking (i.e. find out about errors before you actually run the code - so you wont get caught by deferred name resolution)

    -Declarative development. (i.e. You define what the database state should be and the tool works out how to get it to that state, as opposed to you having to author all of the ALTER statements)

    -Code analysis (i.e. it highlights bad coding practices)

  • Jamie Thomson (3/10/2011)


    The big benefits as far as I can see them are:

    -Development-time error checking (i.e. find out about errors before you actually run the code - so you wont get caught by deferred name resolution)

    -Declarative development. (i.e. You define what the database state should be and the tool works out how to get it to that state, as opposed to you having to author all of the ALTER statements)

    -Code analysis (i.e. it highlights bad coding practices)

    The second one does look like it might swing it. Up to now, we've tended to hand-write upgrade and rollback scripts for each release. It works, but it's time-consuming and quite clunky. I imagine this would be an improvement on that approach.

  • Duncan Pryde (3/10/2011)


    Jamie Thomson (3/10/2011)


    The big benefits as far as I can see them are:

    -Development-time error checking (i.e. find out about errors before you actually run the code - so you wont get caught by deferred name resolution)

    -Declarative development. (i.e. You define what the database state should be and the tool works out how to get it to that state, as opposed to you having to author all of the ALTER statements)

    -Code analysis (i.e. it highlights bad coding practices)

    The second one does look like it might swing it. Up to now, we've tended to hand-write upgrade and rollback scripts for each release. It works, but it's time-consuming and quite clunky. I imagine this would be an improvement on that approach.

    Definitely. On a recent project we moved to a 2-weekly release cycle. We could never have done that if we'd had to manually author our DB upgrade scripts.

    I won't say there aren't caveats to this -nothing is that simple when data is involved- but you'll find that nearly all scenarios are possible.

  • Jamie Thomson (3/10/2011)


    Duncan Pryde (3/10/2011)


    Jamie Thomson (3/10/2011)


    The big benefits as far as I can see them are:

    -Development-time error checking (i.e. find out about errors before you actually run the code - so you wont get caught by deferred name resolution)

    -Declarative development. (i.e. You define what the database state should be and the tool works out how to get it to that state, as opposed to you having to author all of the ALTER statements)

    -Code analysis (i.e. it highlights bad coding practices)

    The second one does look like it might swing it. Up to now, we've tended to hand-write upgrade and rollback scripts for each release. It works, but it's time-consuming and quite clunky. I imagine this would be an improvement on that approach.

    Definitely. On a recent project we moved to a 2-weekly release cycle. We could never have done that if we'd had to manually author our DB upgrade scripts.

    I won't say there aren't caveats to this -nothing is that simple when data is involved- but you'll find that nearly all scenarios are possible.

    That's good to know - we've wasted quite a lot of time in the past testing and debugging upgrade scripts (someone always forgets to add something!)

    Thanks for all your extra information - it's been really useful.

    Duncan

Viewing 15 posts - 1 through 15 (of 29 total)

You must be logged in to reply to this topic. Login to reply