- #WINDOWS 2011 QUICKEN DATABASE SERVER FULL#
- #WINDOWS 2011 QUICKEN DATABASE SERVER CODE#
- #WINDOWS 2011 QUICKEN DATABASE SERVER PROFESSIONAL#
I could open SQL Server Configuration Manager, which meant I could control the service startup options, the network protocols, and trace flags. I was able to run SELECT from sqlcmd and get a result. SQL Server 2008 (64-bit)Ĭomments: I only installed the database engine, and it worked fine. Summary: It didn’t work, but I didn’t bother digging too deep because databases in 2005 and higher compatibility level can be attached and restored on SQL Server 2016+, which makes it moot. Perhaps it just needs the sqlservr.exe to run in an earlier Windows compatibility level, but I didn’t try. I expect if I wanted desperately enough to get it to work, I could shim the registry key it’s failing on and get it working. NET 3.5 feature in Windows Server, it gets all the way to the end before throwing an error about a corrupt registry key while trying to start the SQL Server service. SQL Server 2005 (64-bit)Ĭomments: This one is sneaky because it lets you get very far in the process before failing. If you need to host a SQL Server 6.5 or 7.0 database, this is the way to do it, but I’d do it on Windows Server 2003 R2 instead.
#WINDOWS 2011 QUICKEN DATABASE SERVER FULL#
As I only tried installing the database engine and client tools, I did not bother with the things like replication and full text search. SQL Server 2000 (32-bit)Ĭomments: SQL Server 2000 needs to be installed using Windows compatibility mode (I used XP Service Pack 3). The installer is different to the 6.5 one (which reminded me of Windows 3.x days), and it just didn’t let me get far enough to manipulate the installer files appropriately.
#WINDOWS 2011 QUICKEN DATABASE SERVER CODE#
SQL Server 7.0 (32-bit)Ĭomments: SQL Server 7.0 was Microsoft’s rewrite of the Sybase code base, where a significant number of changes were made to the SQL Server database engine. Obviously this is not for production use. The service is very fragile, and the process does not survive operating system restarts without some handholding. Summary: It works, but I don’t recommend it.
Installation relied heavily on Windows compatibility mode, as well as renaming system files and the associated INI files that referred to those system files to avoid name collisions.
SQL Server 6.5 (32-bit)Ĭomments: This was really tricky to get running, and it isn’t at all stable. Supported versions of SQL Server and Windows Server, adapted from a matrix by Glenn Berryīut I know you’re not here for supported versions, because this post is about what Randolph managed to get running on Windows Server 2019, which as you know is a 64-bit operating system. For official purposes, this is the list you should refer to: SQL Server Version Speaking of documentation, Glenn Berry has a nifty compatibility matrix to show what versions of SQL Server are supported on each version of Windows Server. Last year when Windows Server 2019 was released I wanted to see which versions of SQL Server I could run on it, testing more the unwritten backward compatibility promise Microsoft has maintained over the last 45 years, rather than what the documentation says.
#WINDOWS 2011 QUICKEN DATABASE SERVER PROFESSIONAL#
I don’t consider myself a professional or hobbyist hacker, though if the shoe fits… One of my hobbies is trying to break technology so that you don’t have to.
0 kommentar(er)
