Is Sql Server 2012 Compatible With Windows Server 2019

[Emerio Boykins]

Toinstall Windows Server correctly, your computer must meet the minimum hardware requirements outlined in this article. If your computer falls short of these requirements, the product may not install properly. Actual requirements vary based on your system configuration, applications, and features that are installed.

Unless otherwise specified, these minimum hardware requirements apply to all installation options (Server Core and Server with Desktop Experience) for both Windows Server Standard and Windows Server Datacenter editions.

The highly diverse scope of potential deployments makes it unrealistic to state recommended hardware requirements that would be generally applicable. Consult documentation for each of the server roles you intend to deploy for more details about the resource needs of particular server roles. For the best results, conduct test deployments to determine appropriate hardware requirements for your particular deployment scenarios.

Processor performance depends not only on the clock frequency of the processor, but also on the number of processor cores and the size of the processor cache. The following are the processor requirements.

Computers that run Windows Server must include a storage adapter that is compliant with the PCI Express architecture specification. Servers classified as hard disk drives must not use Parallel Advanced Technology Attachment (PATA) for persistent storage devices. Windows Server also doesn't allow PATA, Advanced Technology Attachment (ATA), Integrated Drive Electronics (IDE), and Enhanced Integrated Drive Electronic (EIDE) for boot, page, or data drives.

Thank you. I came across a few posts that had 2016 and 2019 seems both OP had commented to update BIOS in order for it to work. Which I have done so as well as updating the 6/i firmware. I will give it a try later this week and report back

I have a R610 & R410 running Server 2019 but we changed the PERC RAID adapter as you may have issues finding drivers. Then also installation of OS is a real hassle. WE moved to ESXi then installed VMs. Note, the server is used for test & lab, not production.

I have never had any issues with using the Dell Windows based installers to install the Dell firmware updates under Windows Core/Hyper-V Server. Just download the update via another machine and copy it over or run it over the network.

If I had a 2012 license and needed to pay for a 2019, I am not sure that I would do that. Do you plan to keep the R710 beyond the extended support date of 2012? I think it goes end of extended supportnin 2023.

Confirming Dell PowerEdge R710 works flawlessly with Windows Server 2019. We have a couple of them running Hyper-V virtual machines on top of a core edition, and everything is managed using RSAT (in some cases) and Windows Admin Center -us/windows-server/windows-admin-center primarily. A step-by-step deployment guide can be found here -admin-center-for-windows-server-2019-getting-started . The recent versions have Device Manager already implemented, so installing and managing drivers is no longer an issue. Yet, as far as I remember, all the drivers were detected and downloaded automatically via Windows Update.

For everything else, or older servers, I create a folder called Software on the root of the C: drive for my core servers (which is almost all of them) and copy any installers there using the admin share.

In order to add network adapters to guest machines, you need to configure a virtual switch in Hyper-V first. The official guide covers the matter pretty excellent Create and configure a virtual switch with Hyper-V Microsoft Learn .

Since Windows Server 2019 and 2022 are very similar in terms of the codebase, I am pretty sure you can manually point the Device Manager wizard to the required INF files for previous Windows Server operating systems and it will work without issues. At least that approach is definitely worth trying.

Upgrading the RAID controller to H200 or H700 is a good Plan B option.

What I was wondering was if someone with H700 controller can start the inplace upgrade setup (initial check which reports if all is compatible). If all would be ok, only than I would upgrade the controller to H700.

Another option is to install SSD HDD in a caddy in place of the existing ODD to install the OS on it and get rid of the whole internal RAID controller and map the storage with iSCSI from a SAN since this will only be for backup. The internal SATA controller is only SATA2 but this should do the trick but not redundant solution. For redundancy to run at least mirrored drives we would need PCIe SATA controller card but again would need to look for what would work in this server.

While upgrading the OS on the physical level might be complicated or impossible due to hardware incompatibilities, there is always an option to run a virtual machine with Windows Server 2019 plus SQL 2019. That should work on top of Hyper-V without any issues. Just make sure you have proper licensing.

One more valid alternative is running the new SQL in Azure -v.io/smarter-keep-databases-azure-sql-vs-microsoft-sql-server-vm/ until you upgrade your on-premises infrastructure and migrate everything back.

When we try to install Windows Server 2019 on the very similar model Dl380p G8, the Windows setup is aksing for the Smart Array Controller driver and no matter which version we try to feed it, it just doesn't accpept it. We would like to put our old servers to good use for a testing platform, so all we really need is a working driver for the P420i controller. Any recommendations?

Funny, we started over and used this time an older ISO of Windows Server 2019 which is dated November 14. 2018. With that ISO the installation went through without even asking for a driver. No that's weird...

I tried to install 2019 on a gen 8 proliant DL360P and it seemed to install without a hitch. But after awhile it started rebooting by itself. I figured it was just incompatible, but there is your post. Do you think my server rebooting is something that could be fixed? Any ideas on how to diagnose the problem?

I got this working using intelligent provisioning on a DL360p Gen 8. Have an old decommissioned server experimenting with.

First you have to download and create usb iso for IP 2.80 for gen 9 but will work with and install fine on gen 8.

After IP boot F10 and select 2019 ISO it will eventually blue screen near end after it installs updated bad matrox video driver. What has to be done now is get it to safe mode - usually after a couple blue screen crashes and reboots it will prompt and allow for startup option to select safe mode - maybe possible to use F8 but was difficult for me because I was doing all remotely via iLO and had usb plugged in with images etc. and kept getting press any key to boot from usb so couldn't do F8. Then uninstall bad matrox driver and reinstall an older one from 2016 that doesn't crash (same one in SPP). After that everything works and can apply the full 2017 SPP.

If this issue occurs when trying to integrate Command Line Tools into JetBrains PhpStorm 2019.3.x, check out the current status of this PhpStorm issue, and if it's not fixed in the latest version, use the VC runtime copy workaround described here:

you need first to go to C:\Windows\System32 search for vcruntime140.dll rename it vcruntime140_backup.dllsecond thing is go to xampp path for example C:\xampp\mysql\bin search for the same file vcruntime140.dll copy & paste into C:\Windows\System32

I found the top answer on this page and installed Microsoft Visual C++ Redistributable for Visual Studio 2019 and when I ran the server again it still retuned an error.I noticed from the error log that after the PHP update PHP was being read directly from the C drive.

Since I kept getting this error although vcredist was newly installed, I checked the vcredist files themselves. It turned out that there was an orphan vcredist file in the apache/bin folder which caused the problem.

method 2: if you have visual studio 2015 or above installed on you systemgoto windows\system32 and search for vcruntime14.dll and copy that file and replace it with vcruntime14.dll exists in Xammpp\apache\bin

PHP for Windows requires Microsoft C and C++ (MSVC) runtime libraries and VCRUNTIME140.dll is the main library. You have an older version than the current PHP version was built with. Update MSVC to the latest version and you will be fine.

@Yoann same issue here. Clean install of Windows Server 2019 latest build, install .NET Framework offline installer 4.8, reboot and boom. Many native control panels, like Server Manager, requesting some 4.0.... version of .NET framework instead, failing to load.

I had the same issue and received zero help or support from Microsoft. Dell support googled and read back to me everything I had googled and tried already. Importing the above registry information fixed it without a reboot.

@DavidSherrill This is the exact fix! For us, our RMM tool stopped working on a server 2019 standard server. It's services wouldn't start. Event Viewer complained about .net. Also server manager wouldn't open with the exact message you mentioned. Applying this fixed it all. thanks!!

YOU ARE AN ABSOLUTE LEGEND! THANK YOU! THIS IS THE ONLY SOLUTION THAT WORKED! Every other solution I've googled of this problem has been some variation of "turn net framework on/off in the "turn windows features on or off" app" or "reinstall the newest version of .net" or "did you try restarting your computer?" (OF COURSE I TRIED RESTARTING MY COMPUTER!! DO THEY THINK I'M AN INFANT??)

3a8082e126