Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MAP is finding SQL Instances that don't exist

Unanswered MAP is finding SQL Instances that don't exist

  • Wednesday, April 18, 2012 3:28 PM
     
     
    Sign In to Vote
    0

    A very long time ago we had a three-node cluster with SQL 2005 on it. SQL was moved to a non-clustered machine, and later updated to 2008. Only one node of the old cluster is still running. That node shows no signs of having SQL installed. But MAP tells me that SQL 2005 is there. Map also tells me that the Database Size on that node exactly matches the database size of the real current database (running on a different machine, under SQL 2008.)<o:p></o:p>

    Where is MAP getting its info from? How can I convince it that the old cluster node is not running SQL?<o:p></o:p>


     
     

All Replies

  • Wednesday, April 18, 2012 11:29 PM
    Moderator
     
     
    Sign In to Vote
    0

    My guess is that MAP is pulling some info from the registry that may not have gotten removed during the uninstall of SQL Server 2005. What report and worksheet you are seeing this information? It may be possible that there is a bug in the code that is seeing some residual info from the cluster days and matching it to the existing DB. If that is the case, then the data should not show up if the real SQL Server machine is not inventoried.

    Start a new database and choose the same inventory scenario you did to get the current results. But for the discovery method, use the manual entry and just put in the machine with the ghost info. After doing the inventory, run the report and see if it still shows the data.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Friday, April 20, 2012 1:29 PM
     
     
    Sign In to Vote
    0

    Thanks fro the reply Michael.

    As you suggested, I ran the report (SQL Server Database Details) on a new db, with only the old cluster node.  Same results as before; the cluster node has a SQL 2005 database that looks (in name, file groups and size) just like my active SQL 2008 database that is runing on another server. 

    I searched the cluster node's registry for the DB name, but did not find it.  Perhaps the data is coming from Active Directory?

     
  • Friday, April 20, 2012 9:58 PM
    Moderator
     
      Has Code
    Sign In to Vote
    0

    MAP determines if SQL is installed on a machine with the WMI query 

    SELECT * FROM Win32_Service

    and looks for the SQL service. If it sees the SQL service on the machine, then it will continue to query for SQL information. If you only run the “Windows computers” scenario, MAP will collect some information about SQL such as version and edition because that is in the registry.

    Go to the old SQL Server 2005 node machine; open the run command and type “WBEMTEST”. Then click the “Connect” button and make sure it has root\cimv2 in the namespace and click “Connect”. Then click the “Query” button and enter 

    SELECT * FROM Win32_Service WHERE Name LIKE ‘%MSSQL%’

    If it returns data, then the SQL service is still running on the machine. If it doesn’t return data, then my suspicion is DNS is redirecting to the current SQL Server.

    To quickly check this, you can open the database from the original run and generate the hardware summary report. If the hardware reported is of the new SQL Server 2008 machine and not the old SQL Server 2005 node, then a redirect is occurring.

    If that isn’t an option because they both have the same hardware, then you can test this by going to the MAP machine and running WBEMTEST again, but this time make sure the namespace is \\[HostName]\root\cimv2 and the same WMI credentials you used for the MAP inventory are used. (Remember: If it is a domain account, it must be domain\user or user@domain) Make sure you use the host name or FQDN and not the IP address. Run the same query as before and if my suspicion is correct you will get data returned.

    *edited: Removed info about the DB size not being collected from WMI. I was looking at the wrong properties, it is collected by WMI query.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.