SQL Developer Edition

We are trying to setup a development server with a copy of our live environment that we can use for creating form personalization's and testing uplifts. We are receiving conflicting information on if we can successfully use SQL Developer Edition for this environment. Is anyone familiar with this or use Developer Edition successfully?

Find more posts tagged with

General Discussions

Accepted answers

All comments

unknown

SQL Developer can be used to setup a simple, single user development environment. This would be an unsupported version but can provide a way to develop personalizations that can be transported back to your production environment. Note the limitations that MS puts on this version, specifically that it is not to be used for production systems and cannot be licensed.

If you have a licensed version of SQL Enterprise however, you can setup development and test databases next to your production data and do development in that database and not have to deal with any limitations. This can also be licensed for your development and test databases with a limited user license to support multiuser development.

Please let me know if you have any additional questions.

Ryan Pukanski

I am not sure which Infor products you own, but we have CSI10, PLM Accelerate, CPQ 9.1, Infor OS 2020-12 and have 0 issue with SQL developer 2019.

One thing to keep in mind is your versions as well. We had Syteline 9.30 Multisite which needs SQL partitioning. This was only available on Enterprise editions, prior to SQL 2016. 2016 added a lot more features. If you run standard as your production SQL edition and developer as your dev system, there is a very small chance you could develop something in dev that might not be compatible with standard. When on your dev sql system you can run a select statement to see if there are any features active in your dev database that may not be compatible with standard.

https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-db-persisted-sku-features-transact-sql?view=sql-server-ver15

mtolliver

We currently have our development environment setup on the same SQL Enterprise as our production. When are doing uplifts and refreshing the development databases we are having to start and stop services and reboot the SQL Server. So we were told that to prevent any interruption for our test/dev database we would need to have it on a separate SQL server. Would you agree that is how we should have it setup or is it not necessary to interrupt the production to refresh the other databases and uplift the environments?

Rees Howel

Depends on your product. My experience is with Syteline/Cloudsuite Industrial and while I would normally recommend completely separate Production and Test/Dev servers, it's not absolutely essential at the SQL level. When refreshing Syteline databases, the only service I'd recommend you stop is the SQL Server Agent (just in case a scheduled SQL Job gets kicked off in the middle of the refresh process. If a completely separate SQL server is too difficult, you could just install a second SQL instance on the same server. This would give you separate SQL Server and SQL Server Agent services for each instance, so you can stop and start one environment without affecting the other.

With Syteline the bigger problem is the Utility server and while Infor's hardware guide won't say it's 100% essential I would always have separate Test and Production utility servers

mtolliver

We have Syteline/Cloudsuite 10 so this information is very helpful. I am going to review with our IT and see if we can make a plan to move forward. Thank you very much for all the details.

mtolliver

Thank you very much for the information.

Copyright © 2025 Infor. All rights reserved.