![]() ![]()
have (our product along with) SQL 2014 Developer Edition installed in our QA server, and have QAs test on that server.I am currently developing a new PL/SQL plugin ( language: "plsql", key: "plsql-cop") for SonarQube (using sonarqube-5.0.1), my PL/SQL "checker" is an external java program which is analyzing the PL/SQL code and creates an XML report with all the found recommendations. ![]() Would lilke to know whether this is true as this also my understanding and how I would love to use Developer Edition.Į.g. It doesn't matter you using Developer SQL edition or not, you do still need a CAL. License model, you will need a CAL license. If you need to access production server and you are running in server/cal So to summarize, if you say restore a prod DB to your developer edition SQL server, and only use for development and not serving any clients apart from your own development, that is fine. I'm not a license expert, but here is my understanding of it.ĭeveloper edition is used for development, as long as the data and the purpose is not used as production, that is included.Īs for "CAL", you are correct that for any user/device connects to a production SQL, it will need a CAL license (given you are still on the server/cal model), if you are running on the per core model, you do not need CALs anymore. That means you need to license QA copies of SQL Server as production in order to test your changes and test deployments because you will be refreshing data from production to do the testing. Here is the software, but don't touch it with productionĭata to test against. But based on the text, if I pull the data from production and use it to test its a violation because it touched production. Means copying data to an instance to troubleshoot and tune.etc. Only the tools are, that is considered production use? The tool pack you get in each edition (ssms) is exactly the same, so what difference does that part make if the tools were from developer, standard or enterprise edition? And troubleshooting problems ![]() #PL SQL DEVELOPER LICENSE KEY FREE INSTALL#I understand what the edition is for, and that is why I would install it locally to do work against in regards to dev/test, however, by simply using the tools to connect to production even if the instance on my system is not doing anything with production, There is literally no reason to use the developer edition of the product if that is the case. So, my question is, what use is it then if you can't use it on your system? Even if you installed it on a "server", technically you couldn't pull production data to it, which violates the license. While I would understand the need for a "CAL" license to connect to those production systems, you shouldn't need anything else to run Developer Edition. ![]() While pulling data from a production database for troubleshooting issues, fixing code.etc. I was always under the impression that if you were not "serving" data to production systems, then it was not considered production. If the system has access to a production system, you cannot use Developer Edition on it. He was also told that Developer Edition is not for use with production data, meaning you cannot put production data on it for testing/developing because, well, as a DBA using the tools portion to access production systems, or reading emails.etc. #PL SQL DEVELOPER LICENSE KEY FREE PC#So, Microsoft recently made Developer Edition free to download and use, but during a discussion with a colleague who was being going through reconciliation he was told that you cannot download and use Developer Edition on a PC that you are using for regular ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |