Do you know what you installed while custom installing SQL Server 2022?

 When you install any software in Windows OS, the key information gets into the Registry and some of which you can look up in the control panel.

For example, I Custom installed SQL Server 2022 on 9/14/2024. I see the following entries in the Control Panel/Programs/Programs and Features.

Browser for SQL Server 2022----------9/15/2024

Microsoft OLEDB Driver for SQL Server-9/15/2024

Microsoft SQL Server Setup(English)--9/15/2024

Microsoft SQL Server 2022(x64Bit)--9/14/2024

However, the installation does more than this.

Browser for SQL Server 2022: This service helps clients find SQL Server instances on the network. It’s essential for managing multiple SQL Server instances on a single machine1.

Microsoft OLEDB Driver for SQL Server: This driver allows applications to connect to SQL Server databases using OLEDB, a standard API for accessing database management systems2. There is an associated OLEDB Manager GUI.

Microsoft SQL Server Setup (English): This entry represents the setup files and installation resources for SQL Server 2022. It includes the necessary tools and configurations for installing and managing SQL Server.

Microsoft SQL Server 2022 (x64Bit): This is the main SQL Server engine, which includes the core database services and features. It’s the primary component that handles database operations.

SQL Server 2022 like its predecessors a Windows service. It is a good practice to take a look at what it is.  Therefore, all SQL Server Services can be found in the Windows Services listing as shown here (just pop-up the Services from Control Panel, or just type Services in the Windows Search on the desktop). It is too important a tool and the used should get a handle on this.

There are couple of services that came up with our custom installation we discussed earlier.(link here).The SQL Server related services are all shown inside the red rectangle. If you are unfamiliar with this screen, it is important to understand how things work on Windows.

Let us just look at the SQL Server instant we installed earlier. 

This service is described on the left with your cursor on the service in the left. This service as seen in its properties provides storage, processing and controlled access of data for rapid transaction processing. If you encounter an error that the service is not running etc. you should immediately get to this screen and start the service from this screen.

Note that from this screen, you can not only start but stop, restart (if stopped),or temporarily pause the service. In the Services window shown above place your cursor and make a left click and from the drop-down list, pick Properties.

The Log On tab shows the present long on credentials of the Regency Server. You can make changes in this screen, if you want to.

 

This tab Recovery shows the steps you can take in case the service fails.

The Dependencies shows the interconnectedness of services, system groups etc. The four components shown at the bottom of the next screen all depend on SQL Server.

In earlier versions of SQL Server that I worked with the SQL Server Configuration Manager was installed when the SQL Server was installed and there used to be a shortcut in even earlier versions inthe start menu. However, this shortcut was missing in SQL Server 2016. The link explains why it was moved out of the start menu.

https://hodentekmsss.blogspot.com/2016/10/sql-server-configuration-manager.html

In 2022, there is no such shortcut or link. 

SQL Server Configuration Manager is a very important tool that you may have to access to configure network protocols, manage network connectivity of clients connecting to the server. In SQL Server 2022(16.x) later you can also manage Azure extension for SQL Server.

This link https://learn.microsoft.com/en-us/sql/relational-databases/sql-server-configuration-manager?view=sql-server-ver16, shows where it is located for various versions of SQL Server.

Just type in SQLServerManager13.msc in your Run command (that can be invoked from Search box in Windows 11) as shown,

On clicking OK, the Sql Server Configuration Manager pops-up as shown.

In future posts we look at logging on to the server and other activties.

 

Workaround for the SQL Server 2016 CTP2 installation error

The installation is fully documented here and here.

It was noted previously that the installation did not succeed and several errors were flagged.

Looking at the errors it appears that the installation wizard may not have retrieved the username for Windows Autheenticaiton which it does automatically through the interactive windows assosiated with User/Group.

However looking around a workaround was found which seems to indicate that the SQL Server Installation Center program may have other bugs since installation did not succeed.

In the Services page of Control Panel the property of the SQL Server 2016 was changed to this. The original Log on as; was, This account with( .\Jayaram) and masked passwords.

 

LocalSystemAccount.png

This required stopping the server and starting again. When the server started the SQL Server Management Studio 2016 did not have any problem in connecting to the server with the same credentials (Hodentek8/Jayaram) displayed in the Connect to Server window.

 

The next picture shows Object Browser in the SQL Server Maangement Studio 2016.



ObjectBrowser2016

Details of SQL Server 2016 Version installation