|
As the title says: I have clients that want to run 2 pieces of practice management on the same computer (databases will be on different servers). One piece of software uses Adaptive Server 16 and the other uses Microsoft SQL 2008. The Microsoft SQL is basically the same thing as Adaptive as I understand it but I'm not sure if they will conflict or not but I'm thinking that they probably will. Thanks in advance. |
|
> Microsoft SQL is basically the same thing as Adaptive They are not even close to "the same thing". > I'm not sure if they will conflict or not but I'm thinking that they probably will. They will not. Thank you Breck, I really appreciate it.
(19 Feb '18, 11:46)
shamby
|
|
SQL Anywhere is designed to "place nice" with other applications. I.e. it will attempt to keep its memory usage to a minimum if other applications appear to need the memory. So for example, if SQLA notices that the system memory usage is near or over the real amount of memory in the computer then it will attempt to free some of its cache so that the system as a whole does not thrash. This is normally a good behaviour but can cause poorer database performance if other applications on the computer continue to over-consume memory. I do not know how MS SQL 2008 will behave? My recommendation would be to fix the cache sizes of both database servers (or at least limit the amount of memory - e.g. use SQLA's -ch switch) so that the amount of memory used by both servers is not greater than the total amount of memory on the computer. (You may also want to leave room for other applications - the amount to leave will depend on what else is to run on the same computer). The other consideration is CPU usage. If workload on each of the servers is intensive then the two servers could compete for processing time on the CPU(s). If CPU usage becomes an issue, you should consider restricting the cores used by each server. (E.g. see SQLA's -gta switch available in v17, otherwise see -gtc switch) HTH 1
In my understanding the question is about using different clients on the same machine, not different database servers.
(16 Feb '18, 16:08)
Volker Barth
Replies hidden
1
Doh, yep, you are correct. Breck is correct, SQLA and MS SQL clients will not conflict.
(18 Feb '18, 19:47)
Mark Culp
2
FWIW Mark's answer is also correct, about SQL Server and SQL Anywhere servers cohabiting on the same computer: There are no conflicts whatsoever, none, nada... I do it all the time. Mark's comments about performance considerations are well made... BUT... those kind of worries apply to ANY TWO executables sharing the same computer. Also FWIW, by default SQL Anywhere "plays nice" with other load hogs, by giving up resources when MsBully.exe starts to run (dynamic cache sizing, dynamic multiprogramming tuning).
(19 Feb '18, 07:29)
Breck Carter
|
Do you mean SAP SQL Anywhere (formerly named Adaptive Server Anywhere - ASA) or SAP Adaptive Server Enterprise (ASE)?
That statement is/was true for ASE, not for SQL Anywhere.
Thank you for responding, I really appreciate the help. SAP SQL Anywhere is the database, sorry, I got a little confused with the name changes.
Easy to do! Aide Memoire (simplified...ish I think):
Watcom SQL > SQL Anywhere > Sybase Adaptive Server Anywhere > Sybase SQL Anywhere > SAP SQL Anywhere
Sybase > split into MS SQL Server & Sybase Adaptive Server Enterprise > SAP Adaptive Server Enterprise (aka ASE)
To add some memoires on the ASE side...: I guess the split between Sybase and MS SQL Server was before the re-branding of Sybase as ASE. We started with MS SQL 4.2 (on OS 1.3), which was basically the "PC version" of Sybase at that time (around '93), then moved to Sybase System X and XI (on NT) and then switched to MS SQL 6.0 and later, basically because our admins preferred MS SQL software...
Gladly we got to know SQL Anywhere at that time...