Скачать или смотреть How to Determine Installed SQL Server Instances and Their Versions

A comprehensive guide to finding installed `SQL Server` instances on your network using SQLCMD and OSQL commands. Discover how to reveal hidden instances as well.
---
This video is based on the question https://stackoverflow.com/q/141154/ asked by the user 'Luke' ( https://stackoverflow.com/u/327/ ) and on the answer https://stackoverflow.com/a/141211/ provided by the user 'George Mastros' ( https://stackoverflow.com/u/1408129/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, comments, revision history etc. For example, the original title of the Question was: How can I determine installed SQL Server instances and their versions?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 2.5' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 3.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Determine Installed SQL Server Instances and Their Versions

If you're managing a server environment, knowing which instances of SQL Server are installed can be crucial for maintenance, upgrades, and debugging. Whether you've installed SQL Server manually or it came pre-installed on a system, you may find yourself wondering: How can I determine what instances of SQL Server or SQL Server Express I have installed?

The challenge arises when the methods usually suggested, like running SQL queries, require you to already be connected to a specific instance. Thankfully, there are simple command-line methods to uncover your installed instances without needing to connect to each one individually.

Solution Overview

There are two main command-line tools you can utilize: SQLCMD and OSQL. Both commands can help you list SQL Server instances on your network, giving you a clear overview of what’s available. Below, we'll take a closer look at how to use these commands effectively.

Finding SQL Server Instances with Command Lines

Using SQLCMD

To discover the SQL Server instances on your network, follow these steps:

Open Command Prompt: You can do this by searching for "cmd" in your Windows search bar.

Run the following command:

[[See Video to Reveal this Text or Code Snippet]]

This command will output a list of SQL Server instances available on your network.

Using OSQL

Alternatively, you can achieve the same result using OSQL. Here’s how:

Open Command Prompt.

Run this command:

[[See Video to Reveal this Text or Code Snippet]]

Note: Ensure you use a capital L when using these commands to list the instances.

Understanding Visibility Settings

Sometimes, not all SQL Server instances are visible in the list generated by the above commands. That's because certain instances can be configured to hide themselves from the network. Here’s how you can identify if an instance is hidden and how to unhide it if needed:

Checking for Hidden Instances

Open the Command Prompt.

Run the following command to configure the SQL Server Network Utility:

[[See Video to Reveal this Text or Code Snippet]]

In the SQL Server Network Utility, look for the Enabled Protocols list.

Select TCP/IP, and then click on Properties.

Look for the checkbox labeled Hide server. If it is checked, this instance is hidden from your network view.

By unchecking this option, the instance will start appearing in future listings when you run SQLCMD or OSQL commands.

Conclusion

Knowing how to find the installed SQL Server instances on your network is a valuable skill for any database administrator or IT professional. With these simple command-line tools, you can quickly and efficiently gather the information you need. Remember to check for hidden instances if not all of them are showing up in your results.

Using the commands SQLCMD -L or OSQL -L can save you a lot of time and frustration in managing your SQL Server environment. So, next time you're unsure of what SQL Server instances are present, you now have the tools to discover them effortlessly.