SQL Server Configuration Management - Topology

Hi Experts The main motivation for configuration management SQL server  is the desire to oblige the growing need for a comprehensive view of the SQL-server portfolioin our company. Creating a layout of this hodgepodge will provide a powerful toll in the process of managing both licensing and consolidation candidates.

Can you please help me in how to go about it and what are the essentials things to keep in mind.Thanks
Who is Participating?
Ryan McCauleyConnect With a Mentor Data and Analytics ManagerCommented:
Once you have a list of servers on your network, I'd connect to each in SQL Server Management Studio and record the results of the following things:

1. Run the command "SELECT @@VERSION". This will tell you a few things about your server, including the major version of SQL Server installed, the service pack level, the build (x86, x64, or Itanium), the OS version and build of the server, and a few other details
2. List the Linked Servers on each - from SSMS, browse to the server, then to "Server Objects", then to "Linked Servers". This will show which other servers the SQL Server fetches data from, so it can be helpful when drawing a map of the interconnectedness of your server farm. It's not the only way to get data remotely, but it's a start.
3. To get the processor and memory specs of each server, you'll need to log on with remote desktop, and that can be tedious, but it's another step if they want to know the specs of each server, that's another step you can take.

Is there any other data in particular they're looking for? Unless they have some specific requirements for what "a comprehensive view of the SQL-server portfolio" means, that's good to at least get started. Once they see that, they may some questions for you, but that should be enough information to give them a general overview, and it's pretty easy to gather.
SandeepiiiAuthor Commented:
Documentation Software for Development
Ryan McCauleyData and Analytics ManagerCommented:
That's a huge undertaking, but I'd start with just listing your SQL Servers (with their specs) and then check the Linked Servers section of each to see which servers fetch data from which other servers. That way, you get an idea of which servers are central, which are tightly-coupled to which others, and which are completely stand-alone.

If you need help getting a list of SQL Servers, you can start with this command (from http://ryanfarley.com/blog/archive/2003/11/11/218.aspx):


Open in new window

This will list all the servers on your network that are currently listening for incoming requests - it's a good place to start.
SandeepiiiAuthor Commented:
thanks for  your reply ,it would be great to tell me few more steps what next to do list..just numbering the steps.
I would accept that as a answer.Once again thanks for your reply.
SandeepiiiAuthor Commented:
Yes solution is complete.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.