ctp? what does it mean

ok ... I have looked around and have not been able to find what CTP means.
This should be an easy one for someone to answer. It seems related to code
releases or point releases ... something. Cant get a hit on a definition ...
Thanks in advance
mjCTP Means Community Technology Preview. CTP's generally do not receive the
same level of testing as beta's so they may not be as stable. They are
intended to provide an early look at the next release.
Brad A. Raulston
"MJ Taft" <MJTaft@.discussions.microsoft.com> wrote in message
news:4F48BD74-B9B7-4FD3-BF71-37E7A96221F1@.microsoft.com...
> ok ... I have looked around and have not been able to find what CTP means.
> This should be an easy one for someone to answer. It seems related to
> code
> releases or point releases ... something. Cant get a hit on a definition
> ...
> Thanks in advance
> mj

CTP version and release version

we have a backup of a database from a release version with version number 9.00.1399 and we wanted to restore it to a server with version number (9.00.1116) CTP release. we were issued a version incopatibility message. is it possible to backup from a 9.00.1399 release with a backup file compatible for a CTP release, is there an available option during backup? thanks!

CTP versions are no longer supported. You should be using the released version of the product.

Ideally, you should be at SP1, as we fixed quite a few bugs there.

Backup is a physical operation. If the structure of the database pages has changed in any way, we have no way to do the conversion during restore. For moving up, we have the logic in the startup code to re-apply the same changes that the upgrade would do. We don't support moving down in versions where the database format is incompatible.

|||thanks kevin

CTP June Dev.Edition:TCP/IP protocol is disabled at default

I have tested Developer Edition CTP June but when I connect to remote SQL Server, "A connection was successfully established with the server, but then an error occurred during the pre-login handshake." error occured.
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

CTP June Dev.Edition:TCP/IP protocol is disabled at default

I have tested Developer Edition CTP June but when I connect to remote SQL Server, "A connection was successfully established with the server, but then an error occurred during the pre-login handshake." error occured.
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

CTP June - Where are Integration Services?

I have just installed the June CTP, during the installation it says that it is installing the Integration Services but they do not seem to be there.

I am happy to admit that I am being dim but I cannot connect using the object browser, nothing is listed if I search for services and there is nothing in the Services list in computer manager.

Can someone explain to me what I am doing wrong? I don't have Visual Studio installed, is that required?

Thanks in advance,
NeilOkay, my bad.

I had installed the wrong version.

Neil

CTP Expiration Dates

Is there a document that lists the expiration dates of the CTP releases? We've a test box still on CTP15 and I was wondering when the CTP will stop working.
There is no paper that lists them all but I think in 15's case it will be soon, its almost a year since it was released.|||The agreed licence statement in the setup tells you that the CTP will loose it licence when the version is pubslihed, so you should either consider to remove or upgrade your current system.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
-