Question Re: Is there a difference between the SQLAnywhere Developer and SQLAnywhere installer? in Technology Q&A

Is there a difference between the SQLAnywhere Developer and SQLAnywhere installer?

Former Member — Tue, 14 Jan 2020 12:16:13 GMT

Hi, I downloaded the installation files SQLA17.exe and SQLA17DEVELOPER.exe and I have noticed that both files are identical. I can use the SQLA17DEVELOPER.exe in combination with a valid licences to install a production server? I see the characteristics of the different editions and I see that the Developer edition is different from the Workgroup Edge edition. Can this imply that the license acquired turns off features of the installer? I have a Workgroup Edge edition licen.

Thanks.

Re: Is there a difference between the SQLAnywhere Developer and SQLAnywhere installer?

Breck_Carter — Tue, 14 Jan 2020 12:58:59 GMT

As far as I know the SQL Anywhere setup.exe files have always been the same for all the editions, with license keys and dblic.exe making individual installations work differently. If memory serves, the cloud setup was different but that's moot now. Internally, the dbsrv17.exe and dbeng17.exe executables have some differences, but you always get both of those when you run a setup.

Re: Is there a difference between the SQLAnywhere Developer and SQLAnywhere installer?

VolkerBarth — Tue, 14 Jan 2020 15:19:05 GMT

I don't know about these two files but you can certainly use a Developer Edition to install a paid version, see that older FAQ. It deals with v12 but applies to newer versions, too, AFAIK.

Re: Is there a difference between the SQLAnywhere Developer and SQLAnywhere installer?

asa25 — Wed, 15 Jan 2020 02:13:49 GMT

This is documented as KBA #1878709.

How can an installation be migrated from a non-production license (e.g. developer edition or evaluation license) to a production license?

Re: Is there a difference between the SQLAnywhere Developer and SQLAnywhere installer?

Former Member — Wed, 15 Jan 2020 13:39:42 GMT

Thank you Breck and Volker.. your comments give to me some ideas to better understand the problem that we have. Basically, we have differences when compare one report in production against the same report in test. Theoretically we have the same servers configuration, but, in production we have a license for Workgroup Edge Edition and Developer Edition for testing.

Re: Is there a difference between the SQLAnywhere Developer and SQLAnywhere installer?

Breck_Carter — Wed, 15 Jan 2020 13:53:23 GMT

If SELECT @@VERSION returns the same result in test and production, look elsewhere for your problem. I.e., there is some difference in the database data, or the SQL code, or the application code between test and production, or, if your application has some dependencies on the outside world (files, etc) the problem may be caused by differences there.

If SELECT @@VERSION is different, the problem may be caused by differences in the server code.

Re: Is there a difference between the SQLAnywhere Developer and SQLAnywhere installer?

Former Member — Wed, 15 Jan 2020 17:33:33 GMT

@@VERSION is the same for both (17.0.6.2806) and data has a two hours difference (from backup). I think that difference is the services and the server licence. For example, in production we have 7 services on the same server holding 18 databases and in testing we have one service mounted for the same 18 databases. Another difference is the engines. While we have a Workgroup Edge Edition license in production, in testing we have the Developer edition.

Re: Is there a difference between the SQLAnywhere Developer and SQLAnywhere installer?

VolkerBarth — Wed, 15 Jan 2020 17:34:47 GMT

Well, even if data and code and server version are identical, results may be different, say because the database engine uses different query plans, and your query is non-deterministic (think of a missing ORDER BY), or because configuration is different.

Re: Is there a difference between the SQLAnywhere Developer and SQLAnywhere installer?

VolkerBarth — Thu, 16 Jan 2020 03:12:06 GMT

As Breck has stated, it's very unlikely that the differing results (BTW: In what respect do they differ?) are related to the editions in use when the build number is identical.

You might check the query plans of the according queries for differences, it could also be related to different cache contents, isolation levels, different concurrent users and the like...