Download Sql Server Management Studio (ssms) UPD
Zayne Plascencia
I have setup a SQL Server 2008 Express instance on a dedicated Windows 2008 Server hosted by 1and1.com. I cannot connect remotely to the server through management studio. I have taken the following steps below and am beyond any further ideas. I have researched the site and cannot figure anything else out so please forgive me if I missed something obvious, but I'm going crazy. Here's the lowdown.
I do a port scan from my local computer and it says that the port is FILTERED instead of LISTENING. I also tried to connect from Management studio on my local machine and it is throwing a connection error. Tried the following server names with SQL Server and Windows Authentication marked in the database security.
First, in management studio, check management, sql server logs\current - you want to search for a message saying 'Server is listening on ['any' 1433].' If not, go to start, all programs, SQL server 2008, configuration tools, sql server configuration manager. Select 'sql server network configuration\protocols for MSSQLServer\SQLExpress'. Ensure TCP/IP is enabled. It should be based on the output of netstat -ano, but...
As mentioned above, SSMS 19.x doesn't upgrade 18.x but will install side by side. If you don't wish to keep 18.x then you should run choco uninstall sql-server-management-studio prior to installing the latest version of this package.
I'd like to propose renaming ssms to sql-server-management-studio. The original tag was created when tags were limited to 25 characters, but I see no reason to keep the abbreviation now that the limit has been increased.
What benefit is derived over renaming, as opposed to simply adding the synonym sql-server-management-studio to the ssms tag? You can do that yourself, right now, if you have enough rep in the latter tag.
There certainly isn't currently a discoverability problem, because if you type sql-server-management-studio in the tags box you get suggested ssms due to one of its existing synonyms being sqlservermanagementstudio.
At the same time, there are arguments against the rename. First, ssms is much, much shorter than sql-server-management-studio. Because of the dramatic difference in length, it could take noticeably longer to scan the tag section if we go with the proposed change (again, my personal opinion). Not the end of the world but the difference might still prove annoying.
Secondly, when editing the Tags section of a question, I like to take advantage of the list of suggestions that shows when I start typing the name of a tag. Now, there are many sql-server-nnn tags already, and the suggestion list shows only 6 items, which are chosen based on their popularity. Currently the number of SSMS questions doesn't make ssms one of the top 6 SQL Server-related tags. However, that might well change in the future, which would mean that sql-server-management-studio would start showing in the suggestion list along with tags related to SQL Server versions or concepts when I start typing sql-server-. Now, fair enough, you will say, if it's popular enough, why not. My response to that is, a tag for something that can work well as an abbreviation should not force out a tag related to a thing that cannot be abbreviated.
df19127ead