How to connect to the June Katmai CTP?

Hi all,

I'm new to the Katmai SQL Server. I have just installed the June CTP x64 developer edition on a Win2003 Server AMD x64 bit. I installed everything. The install went fine.

My question:

How do I connect to the Katmai? There where no Management Studio in the install package.

The SQL Server 2005 Management Studio will not connect. It says that it can only connect to SQL 2000 or SQL 2005.

Best regards,

Lars-Inge

(Lars-Inge Tønnessen@.discussions.microsoft.com) writes: > I'm new to the Katmai SQL Server. I have just installed the June CTP x64 > developer edition on a Win2003 Server AMD x64 bit. I installed > everything. The install went fine. > > > > My question: > > How do I connect to the Katmai? There where no Management Studio in the > install package. There was in mine. Hm, I installed 32-bit. Could it be that tools are in the 32-bit distribution? (Tools are 32-bit anyway.) Also, look for a setup in the Tools directory if there is one. > The SQL Server 2005 Management Studio will not connect. It says that it > can only connect to SQL 2000 or SQL 2005. SQLCMD and OSQL works. And Query Analyzer from SQL 2000, if you have it around. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||I also tried to install SQL 2008 on VPC for Orcas. I see only configuration tools.

How to clean machine for SQL2005 Reporting Services RTM

hi all,

I am trying to get Reporting Services to install on a machine that previously had the September CTP install on it.

The SQL Server part of the install has been fine and all seems to be operational as expected but the Reporting Services fails to install with the following errors:

"An instance of the same name is already installed on this computer..."

This is thrown out of the ValidateInstanceName func in the MSI. I am telling it to use the Default Instance as there is only one SQL instance running (to my knowledge).

How do I clean up the machine so that it does not think another instance is present? I have tried MSIZAP and that has not helped. I have removed references from IIS, COM+, file system and registry.. but there must be some I am missing. Does anyone know what ValidateInstanceName is actually looking at/for?

Thanks
PaulIf in doubt..

Uninstall SQL Server 2005 and remove every reference to SQL (as far as possible) from the registry..

Fixed the issue.