When I last looked into it, it came down to whether or not the data was being used for production purposes. For example - you could use it to test a bunch of orders, but if those orders are going to be real, then it needs a real (non-Dev) license. If you throw away those orders because they were just for test (or demo, for that matter), then you can keep it.
A production environment, even if it's an early-edition, needs a license. To be unlicensed, you need discard the data. Rob On 25 July 2013 10:08, Mark Wills <[email protected]> wrote: > Agree with Greg,**** > > ** ** > > For User Testing, because they are users, they should be covered under > normal Licence.**** > > ** ** > > Assuming they are, then their license will cover them for equal or lesser > editions.**** > > ** ** > > The Developer Edition is pretty much just for development purposes > (including testing) but not for consumers. **** > > ** ** > > We had the same dilemma with our developments, and bottom line came down > to “who” the users really were. Part of the dev team, no problems. Part of > User community, then as long as there were (consumer type) licenses then > they were OK to use the Dev / QA environment and didn’t need a second (Dev > edition) license.**** > > ** ** > > But as Greg also said, you need to sort out that arrangement with > Microsoft and when discussing, be as specific as possible as to what > licenses you already have and the nature of work needing to be achieved > under the Dev Edition.**** > > ** ** > > Cheers,**** > > Mark**** > > ** ** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of * > GregAtGregLowDotCom > *Sent:* Wednesday, 24 July 2013 8:40 AM > *To:* ozDotNet; SQLDownUnder > *Subject:* RE: SQL Server Developer Edition**** > > ** ** > > Hi Corneliu,**** > > ** ** > > It’s good for dev/test scenarios but I gather not for UAT type scenarios.* > *** > > ** ** > > You’d be best getting advice from MS, and as usual, keep asking till you > get the advice you wanted J**** > > ** ** > > I’ve found that in general, no-one in the sales groups understand the dev > edition. Last year, it took them over a week to work out how we could buy > one. Now they are available from the standard license suppliers.**** > > ** ** > > Regards,**** > > ** ** > > Greg**** > > ** ** > > Dr Greg Low**** > > ** ** > > 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913fax > **** > > SQL Down Under | Web: www.sqldownunder.com**** > > ** ** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Corneliu I. Tusnea > *Sent:* Wednesday, 24 July 2013 7:52 AM > *To:* ozDotNet; SQLDownUnder > *Subject:* SQL Server Developer Edition**** > > ** ** > > Hi guys,**** > > ** ** > > [cross post to ozDotNet and SQLDownUnder]**** > > ** ** > > I'm having a bit of trouble figuring out the licenceing of SQL Server > Developer Edition.**** > > ** ** > > This is straight from the SQL_Server_2012_Licensing_Reference_Guide.pdf > from Microsoft:**** > > *Licensing SQL Server for Non-production Use***** > > *When using SQL Server software for development, test or demonstration > purposes, only the users are licensed***** > > *and there is no need for a corresponding license for the actual server > systems running SQL Server software in***** > > *this case.***** > > *[...]***** > > ** ** > > Now, can I assign such a licence to a public test/utc environment we use > to test the application before going into production. The "application" is > a website accessible over the internet but will NOT be used for any > production use. It's purely for testing, staging, utc and performance > testing.**** > > ** ** > > Thanks,**** > > Corneliu**** > > _______________________________________________ > sqldownunder mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/sqldownunder > > -- Rob Farley LobsterPot Solutions http://www.lobsterpot.com.au http://sqlblog.com/blogs/rob_farley @rob_farley
