I need to change the port for a named SQL Server 2008 database instance running on a Windows 7 server.
I went into the SQL Server Configuration Manager and manually changed the ports. I got the warning about having to restart the server to activate the changes. I right-clicked on the server and clicked 'Restart'. It stopped OK, but failed to restart. I tried starting it three times and it always failed.
Then I changed the ports back to the settings they were before the restart, and when I clicked on the server to start, it started right up.
Do I need to change the port settings somewhere else? For example, do I need to update the entries in the ENDPOINT table? I was thinking the worse thing that would happen is that the database would start right up, but I wouldn't be able to see it from some of the remote computers. I was surprised that a port change would cause the database to stop entirely.
One more thing: there are two databases on this server. One is an unnamed default database, and the other (the one I'm trying to change the ports on) is a named instance. The unnamed database has a fixed port number. The named database has 'TCP Dynamic Ports' set to '0' for IP1, IP2 and IP3. It has a 5-digit number for IPAll. The 'TCP Port' value is blank for all four IP cases. I was trying to set the named database to a different fixed port. Is it possible that the named database is somehow tag-teaming off the unnamed database's port?
I'm super new to SQL Server 2008 so this is all confusing to me.
Any help would be much appreciated.