Curious about SQL Registry Entries RRS feed

  • Question

  • I'm working on building some documentation across my systems and planned on simply using Powershell to script out the legwork of what I wanted to do. While that's going all well and good, I ran into an issue with my SQL Server registry entries. The problem being that some of my SQL servers have all of their registry values while some don't.

    For example, I'm pulling down the SQL Shared Features entry so I know where that directory is on all servers. Now some of them are pulling data back (E:\yada\yada) while others aren't pulling anything back. After further investigation, I have noticed that several of my SQL servers don't have the required registration data saved within the registry. This happens with several different registry entries that should be there.

    Any reason it's like this?

    Tuesday, October 8, 2013 6:52 PM


  • We don't really have enough information to comment on this. Computers sometimes follow a complicated path to get to their current state. Different OS version different SQL Server versions. Upgrades to OS and SQL Server might not be in the same order. Different SQL Server Editions, service packs, and different components installed and uninstalled, or not upgraded. Consistency seems unlikely to me. I guess the first question is, for any given registry entry, is that component installed and does it work properly? I am aware that this post isn't much help.

    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

    • Marked as answer by Elvis Long Thursday, October 24, 2013 2:28 AM
    Monday, October 21, 2013 10:39 PM

All replies