This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 52%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hi,
Can we use SQL Express 2019 running alongside your existing full version SQL 2014 on the same server?
We need SQL2014 for Dynamics NAV and would like using SQL Express for DDM(low cost multi-CAD PDM/PLM solution)so I can work from home and not have to remote my work comupter from home?
Thanks!
You can install up to 50 named instances of SQL Server on one machine and all can have different versions and different editions, that's fully supported, see
Thanks Olaf!Much apreciated!
Our DDM software is I think running on our virtual server WC-APP1 along with SQL server 2014.
This supports both our Dynamics Nav 2009 R2 and the running version of DDM
I believe the SQL license we purchased was for SQL server 2017 but we are running 2014 as this is the latest version Microsoft certify for NAV 2009 R2.
The DDM server requirements for latest version 2023 requires at least SQL Express 2019.
We only need the small (5-20 users) configuration so could use SQL Express 2019 rather than full SQL.
I believe the SQL license we purchased was for SQL server 2017 but we are running 2014
And I don't believe, because you can not install SQL Server 2014 with a 2017 product key, that's not possible.
Yes, we dont have an IT department and information Im getting has to be put togheter from different sources.
Dont know what was purchased, what certain is that we have SQL2014 on a 2019 Windows server and wnated to know if we can run SQL Express 2019 on the same virtual server so I dont need to purchase an additional Windows server licence.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 71%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
SQL 2019 express requires at least Windows Server 2016.
So if your current SQL 2014 instance already runs on Windows Server 2016 both instances should coexist.
It realy is painfull to search for old support information about deprecated products... but here it is. SQL 2014 should work on Windows Server 2016. Search for 'SQL Server Express' in 'Breadth Editions Operating System requirements' section.
Some additional guidelines regarding coexistance.
Hope information helps and no heavy lifting (upgrades and migrations :-) will be required.
Regards
Thanks for your reply!
We are running on Windows Server 2019.
I messeged our DDM supplier and the answer we go back was that SQL Express 2019 cant run alongside our existing full version SQL 2014 on the same sever as the operating systems do not support such thing and they will block eachother;
Then he went o advision us the best option is to have two separate servers.
Kind Regards,
Tudor.
Thanks for your reply!
We are running on Windows Server 2019.
I messeged our DDM supplier and the answer we go back was that SQL Express 2019 cant run alongside our existing full version SQL 2014 on the same sever as the operating systems do not support such thing and they will block eachother;
Then he went o advision us the best option is to have two separate servers.
Kind Regards,
Tudor.
Since you are running Windows 2019, you should be able to run two SQL instances on the same machine without any functional conflict. However, they will compete on resources, so you could experience bad performance. And maybe your DDM supplier don't want to take the flak for that, which is why they recommend a different server. There could also be issues with the DDM software itself, although I don't really see what that might be.