November 6, 2012 at 3:08 pm
Can we allocate other than 1433 as port number to default instance ? It should be static and not multiple ports
November 6, 2012 at 3:19 pm
Yes this is no problem. Even though this link is for 2005 it is the exact same process in 2008, not sure about 2012 since I don't have it.
http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/d91d265a-59d3-4c8a-94ad-227611c342d8/[/url]
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
November 6, 2012 at 3:26 pm
Thanks for the reply
i dont see anything mentioned in the link that we can change port 1433 as port number for default instance,
i am sure we can change it for named instance and i have done it.
November 6, 2012 at 3:37 pm
Sean,
Thanks for the reply,
R u sure that we can allocate diiferent port number to default instance. please let me know. This is something urgent.
Thanks a ton!
November 6, 2012 at 3:51 pm
You can do this with the "SQL Server Configuration Manager".
November 6, 2012 at 3:56 pm
Sqlism (11/6/2012)
Thanks for the replyi dont see anything mentioned in the link that we can change port 1433 as port number for default instance,
i am sure we can change it for named instance and i have done it.
Yes, this is something that you can change. You can alter the port number for the default instance of SQL Server to use a port other than 1433. I just tested it on a development SQL Server 2008 R2 instance and it worked fine. Remember from SSMS that you will need to provide the port number when you attempt to connect to the server. I used port 50000 for the test I performed.
November 6, 2012 at 5:22 pm
The reason for chnging the port number is security best practices, for connecting to the instance thru SSMS to the server we should reveal port number to all the developers, i think it is not best practice, but i found a solution whre we can alias the "servername,portnumber = servername" in the following links.
Thanks a ton for the help and testing
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply