Developer Edition

  • I installed a SQL server 2008R2 developer edition on a server and giving RDP access to the developers to the box. Am i doing right here.

    Please let me know what license issues i am breaking if any?

    Thanks!

  • Each developer needs to have a licensed copy of the developer edition. Also, you do realize that if the developers have to RDp to the server, you most likely will only have two developers working at a time.

    They really should have the client tools installed on their desktop/laptop systems and access the developent server from there.

  • That will work but it seems a lot easier to have the developers install SQL on their local. Then they can connect to the sql server from their own desktop. No need to remote in for sql purposes.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Just grant them access to the Dev instance on the server rather than RDP. Then install management tools on their desktops and allow them to use SSMS to connect to the Dev instance to do their development.

    Alternatively, install a dev instance on each developers machine.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • SQLRNNR (7/23/2012)


    Just grant them access to the Dev instance on the server rather than RDP. Then install management tools on their desktops and allow them to use SSMS to connect to the Dev instance to do their development.

    Alternatively, install a dev instance on each developers machine.

    Or both. The development environment on the their machine would isolate their work from others and the development server could be used as an integration server during development.

  • Lynn Pettis (7/23/2012)


    SQLRNNR (7/23/2012)


    Just grant them access to the Dev instance on the server rather than RDP. Then install management tools on their desktops and allow them to use SSMS to connect to the Dev instance to do their development.

    Alternatively, install a dev instance on each developers machine.

    Or both. The development environment on the their machine would isolate their work from others and the development server could be used as an integration server during development.

    That's how my workplace does it.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Wow thats a great response..

    Thanks everyone..

  • You're welcome. Let us know if you need anything else.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

Viewing 8 posts - 1 through 8 (of 8 total)

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