Best way to install PHP, SQL Server Express, IIS on Windows Server 2016?
-
I have backup files from an intranet webapp that was developed 7-8 years ago, running on Win 2003 with IIS, Sql Express and PHP using MS PHP driver (sqlsrv).
What is the best/recommended/easiest way to install PHP, SQL Server Express, IIS on Windows Server 2016?
I want this up and running with a minimum of change to the PHP code.
-
You won't be able to install this on a new system without updating the underlying pieces. It's too old.
If it's that critical, virtualize it and slowly test migrate it to a new environment. (if it's not already virtual).
-
@pete-s said in Best way to install PHP, SQL Server Express, IIS on Windows Server 2016?:
I want this up and running with a minimum of change to the PHP code.
I have feeling this wont go as smoothly as you wish.
But our thoughts and prayers heading your way ...
-
What version of php is it using now? Hope it is at least 5.something
Copying this site to a newer iis is trivial. I did this with an old 2000 web application here, I had to change some permissions after the move, but it wasn't difficult. -
@dustinb3403 said in Best way to install PHP, SQL Server Express, IIS on Windows Server 2016?:
You won't be able to install this on a new system without updating the underlying pieces. It's too old.
If it's that critical, virtualize it and slowly test migrate it to a new environment. (if it's not already virtual).
It depends, what is that is needed, if it is using PHP most of it can be used on a newer system but if not then more problematic... I suggest a dev enviroment and test and then check what doesn't work.
-
I think you might need to use an older PHP, like 5.6 rather than the 7 family. But, other than that, I would not anticipate a need for many changes, if any.
-
I don't have access to the old system but I imagine it being PHP 5.x since PHP 5 was the only stable version under development in 2008 according to wikipedia. And this is from 2010/2011 something.
Is using the MS Web Platform Installer the best way to install this?
PS, it will for sure run on a virtualized server.
-
And how about SQL server express? It's was likely the 2008 version.
Should I anticipate any big changes there or is it likely that the SQL will run the way it is?
BTW, I saw that SQL Server Express 2017 runs on linux as well?!?
-
@pete-s said in Best way to install PHP, SQL Server Express, IIS on Windows Server 2016?:
And how about SQL server express? It's was likely the 2008 version.
Should I anticipate any big changes there or is it likely that the SQL will run the way it is?
BTW, I saw that SQL Server Express 2017 runs on linux as well?!?
Yup, runs on Linux.
-
@scottalanmiller said in Best way to install PHP, SQL Server Express, IIS on Windows Server 2016?:
@pete-s said in Best way to install PHP, SQL Server Express, IIS on Windows Server 2016?:
And how about SQL server express? It's was likely the 2008 version.
Should I anticipate any big changes there or is it likely that the SQL will run the way it is?
BTW, I saw that SQL Server Express 2017 runs on linux as well?!?
Yup, runs on Linux.
You've tried it right?
-
@obsolesce said in Best way to install PHP, SQL Server Express, IIS on Windows Server 2016?:
@scottalanmiller said in Best way to install PHP, SQL Server Express, IIS on Windows Server 2016?:
@pete-s said in Best way to install PHP, SQL Server Express, IIS on Windows Server 2016?:
And how about SQL server express? It's was likely the 2008 version.
Should I anticipate any big changes there or is it likely that the SQL will run the way it is?
BTW, I saw that SQL Server Express 2017 runs on linux as well?!?
Yup, runs on Linux.
You've tried it right?
No, still a bad product that I think you'd be crazy to deploy under normal circumstances. 90% of the cost of SQL Server is SQL Server itself, not running it on Windows. Running it on Linux helps, but retains the core problem of paying an outrageous fortune for a system marginally better than free alternatives - and ones that are easily managed as part of the OS platform. Why do all the maintenance of SQL Server when you can do PostgreSQL essentially maintenance free?
And when you are talking a $50,000 deployment because SQL Server might be slightly faster... take a fraction of that money and put it into better hardware for PostgreSQL. I think PostgreSQL will be faster for cheaper, even if not faster in code.
SQL Server is a great product, but is encumbered by lots of licensing complexity (ergo risk) and incredibly amounts of cost. The Express version is free and that's fine, but why create technical debt rather than avoid it?
So it never really comes up.
