SQL Server Express is a free version of Microsoft’s SQL Server. Access to an administrator-level account.The steps for installing, testing, upgrading, and uninstalling SQL Server Express 2019 are described in detail in the following guide. However, not all users will find these necessary, and many may wish to turn to the more lightweight SQL Server Express instead.
SQL Server 2014 was the last version to support 32-bit, so the issue that I faced this time will be going away.The last several versions of Microsoft’s SQL server have seen the introduction of a number of new features.
You will be provided with a pop-up box containing a choice of files to download – the 32-bit version has x86 in the filename, and the 64-bit version has 圆4 as shown below:
Use the Search Box on the right hand side to locate the patch that you require and then click the “Download” button.
To access Microsoft Update Catalog, navigate to: Enterprise, Standard, Developer or Express Edition. It’s worth noting that the same SP or CU can be used on any Edition of SQL Server – i.e. “Microsoft Update Catalog” allows you to obtain exactly the update that you require. There are times, however, when you need a specific version, for example the third-party application only support a set patch level or if a new CU came out just a few days ago. When you go to download a Service Pack or Cumulative Update, Microsoft will do its best to direct you to the very latest version. There are a few sites that will tell you the latest SP / CU available for SQL Server versions. Getting back to the 32-bit Patch, a few words about downloading patches / cumulative updates. Microsoft SQL Server () () XX.X.XXXX.X (x) This will helpfully tell you whether it is 32-bit (x86) or 64-bix (圆4). Once you log into a SQL Server Instance, you can use SELECT to check the version that is installed. Log in using that Account and give yourself permissions that way. Sometimes, you just need to use the Service Account that the application is using. There are multiple ways to access a SQL Server for which you don’t have access, and I have written about this in the past: What’s more, the application locked down access so that the only account able to log into the SQL Server was the application’s own. A third party Application put it there as part of it’s own install.
So, why was there a 32-bit version of SQL Server there in the first place? Well, I didn’t install it. Perhaps this was the reason that Ivanti didn’t do the upgrade. Since SQL Server treats the two as entirely different products, I can understand that but it would be nice if the Installer actually warned you of the difference instead of just not finding the Instance. Turns out that the installed version was 32-bit, and the patch that I was trying to use was 64-bit.
This allows it to be put on a existing SQL Server that you have full control over – much easier to manage. Where possible, the requirement for a SQL Server Express Edition Instance should be identified up front and the application checked to see if it can be configured to use an existing SQL Server Installation in a different location.