I find out TCP/IP protocol is disabled at default at CTP June. When you meet with same situation, try enable TCP/IP protocol being enabled on "SQL Server Configration Manager"
It's bug or by design?
Regards
Hajime GondoThis is in fact by design. As part of only making available services that you need we are defaulting the Developer Edition to not listen on TCP/IP.
-Euan|||Thanks Euan! I found topic "Network Protocols and Network Libraries".
But I can't accept this design. Bacause developer edition "must" (I think) functionaly works same as enterprise edition. If not, developer must search what is deffernt between Dev. and Ent.(such as me) This causes needless confusion.|||It does work the same as Ent and Std, the defaults are just different(this is the case with SSE as well). We provide a tool to flip the defaults.
-Euan|||It's nice that you will provide the tools. Question is, WHEN, we are waiting....|||There are 2 tools, the commandline version of setup allows much of this to be overriden and the surface area config tool allows you to flip al;l of these things asll, both have been in since the product RTM'd last year.|||
To install via the command line and turn TCP/IP on, specify the DISABLENETWORKPROTOCOLS command line parameter:
;--
; The DISABLENETWORKPROTOCOLS switch is used to disable network protocol for SQL Server instance.
; Set DISABLENETWORKPROTOCOLS = 0; for Shared Memory= On, Named Pipe= On, TCP= On
; Set DISABLENETWORKPROTOCOLS = 1; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= Off
; Set DISABLENETWORKPROTOCOLS = 2; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= On
; Note: DISABLENETWORKPROTOCOLS if not specified has the following defaults.
; Default value for SQL Server Express/Evaluation/Developer: DISABLENETWORKPROTOCOLS =1
; Default value for Enterprise/Standard /Workgroup: DISABLENETWORKPROTOCOLS =2
DISABLENETWORKPROTOCOLS=
To configure the TCP/IP after installation, you need to use the Surface Area Configuration tool that Euan mentioned. This blog entry describes it pretty well for SQLExpress - it applies equally well to other skus. ttp://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
Hope this helps.
-Jeffrey
No comments:
Post a Comment