I installed a Main Polling Engine with a bunch of modules as a lab and used the Express version of SQL. It all went in fine and it worked pretty well, but then I wanted more. I needed to add an Additional Polling Engine and an Additional Web Server so that I could make a closer replicant of my production Orion. I had a proper DBA set up the production SQL, but I was on my own for the lab and I could not access my cheapy SQL from anywhere.
I found that SQL normally installs with TCP/IP disabled. I don’t know why Microsoft think that it’s a good idea to disable the most popular protocol in the galaxy, but although it works fine for a one server lab, it does not work for anything more complex.
To make it work properly, just run the SQL Server Configuration Manager, dig down into the Network section and enable TCP/IP. It warns that it requires a service restart but a server bounce worked well and gave me time to brew another mug of tea.
A very accidental DBA
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.