SQL Server Management Studio can't 'see' the 2005 engine?? But can see 2000 ?!?

Jack

Hello,

I had SQL2000 server running fine on the windows 2003 box. I then installed
SQL 2005 Express. They both worked together fine. I then uninstalled SQL
2005 Express and installed SQL 2005 Server. But when I open SQL Server
Management Studio, I can only connect to the SQL 2000 engine. In the Object
explorer, it says v8.0.2039 (which I think is SQL 2000 Server, because I can
see the existing SQL 2000 databases).

How can I get SQL Server Management Studio to 'see' the SQL 2005 database
engine so I can create tables? I *think* its running because there is the
'sqlservr.exe' process running, and during installation there is no issues.

When I open SQL Server Management Studio, I choose 'Database Engine', then
my local Servername with Windows Authentication. How do I connect to the SQL
2005 instance?

Thanks,
Jack.

Aug 9 '06 #1

Erland Sommarskog

Jack (ja**@nospam.com.uk) writes:

I had SQL2000 server running fine on the windows 2003 box. I then
installed SQL 2005 Express. They both worked together fine. I then
uninstalled SQL 2005 Express and installed SQL 2005 Server. But when I
open SQL Server Management Studio, I can only connect to the SQL 2000
engine. In the Object explorer, it says v8.0.2039 (which I think is SQL
2000 Server, because I can see the existing SQL 2000 databases).

How can I get SQL Server Management Studio to 'see' the SQL 2005
database engine so I can create tables? I *think* its running because
there is the 'sqlservr.exe' process running, and during installation
there is no issues.

Did you actually try to connect to it? Your Express instance was presumably
called SQLEXPRESS, but you did not use this instance name when you installed
Enterprise/Standard edition.

You can use SQL Configuration Manager to view which instances you have
installed, and whether they are running.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Aug 9 '06 #2

Jack

Hi Erland ,

When I open SQL Server Management Studio (SSMS) a window pops up asking me
to 'Connect To Server'. This works fine because when I connect, SSMS
contains the databases that I had previously defined in SQL Server 2000. I
still can't see anywhere to connect to a SQL 2005 instance. I then launch
SQL Server Configuration Manager (SSCM) which contains no information in any
of the items in the tree.

Even if I do not connect using SSMS, SSCM still contains no information in
any of the items in the tree. At:
http://forums.microsoft.com/MSDN/Sho...ID=93&SiteID=1 someone
asked how to create an instance and apparently you have to do this by
putting in the CD and re-run the installation. I did this, but when
selecting " Run the SQL Native Client Installation Wizard" it says that I've
got a higher version and cannot finish. (The reason for this is thatI've
installed the SP1). How can I create a new instance (like, what tool?) so I
can connect to one?

I'm not sure why this is so difficult for me?

Jack.

"Erland Sommarskog" <es****@sommarskog.sewrote in message
news:Xn**********************@127.0.0.1...

Jack (ja**@nospam.com.uk) writes:

>I had SQL2000 server running fine on the windows 2003 box. I then
installed SQL 2005 Express. They both worked together fine. I then
uninstalled SQL 2005 Express and installed SQL 2005 Server. But when I
open SQL Server Management Studio, I can only connect to the SQL 2000
engine. In the Object explorer, it says v8.0.2039 (which I think is SQL
2000 Server, because I can see the existing SQL 2000 databases).

How can I get SQL Server Management Studio to 'see' the SQL 2005
database engine so I can create tables? I *think* its running because
there is the 'sqlservr.exe' process running, and during installation
there is no issues.

Did you actually try to connect to it? Your Express instance was
presumably
called SQLEXPRESS, but you did not use this instance name when you
installed
Enterprise/Standard edition.

You can use SQL Configuration Manager to view which instances you have
installed, and whether they are running.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Aug 12 '06 #3

Erland Sommarskog

Jack (ja**@nospam.com.uk) writes:

When I open SQL Server Management Studio (SSMS) a window pops up asking me
to 'Connect To Server'. This works fine because when I connect, SSMS
contains the databases that I had previously defined in SQL Server 2000.

In this window you can specify a different server instance, for instance
..\MMV if MMV was the name you gave to the SQL 2005 instance. On the
other hand:

I then launch SQL Server Configuration Manager (SSCM) which contains no
information in any of the items in the tree.

It does not seem that you have any SQL 2005 instances installed at all.

apparently you have to do this by putting in the CD and re-run the
installation. I did this, but when selecting " Run the SQL Native Client
Installation Wizard" it says that I've got a higher version and cannot
finish. (The reason for this is thatI've installed the SP1). How can I
create a new instance (like, what tool?) so I can connect to one?

If you already have SQL Native Client installed, there is no need to
install it. Just pick "Server components, tools, Books Online and samples"
under the "Install" header.

Pay particular attention when it comes to selecting an instance. If you
select default instance, you will upgrade you SQL 2000 instance. There is
also a button where you can view installed instances.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Aug 12 '06 #4

Jack

Thanks Erland.

After many, many hours I finally got it working:

When I originally installed SQL 2005 I installed it with the 'default
instance' option. I wrongly assummed that it would have set up a default
'SQL 2005' instance, but what it seemed to have done was take the EXISTING
SQL 2000 instance and treated this as the default. This is why there were no
SQL 2005 instances created.

You have to press the 'Change' button in Add/Remove programs for SQL 2005 to
get the installation running again, and NOT the CD. This is the only way
that I know of to create instances in SQL2005

Again, thanks so for your help and direction.

Regards,
Jack.
"Erland Sommarskog" <es****@sommarskog.sewrote in message
news:Xn**********************@127.0.0.1...

Jack (ja**@nospam.com.uk) writes:

>When I open SQL Server Management Studio (SSMS) a window pops up asking
me
to 'Connect To Server'. This works fine because when I connect, SSMS
contains the databases that I had previously defined in SQL Server 2000.

In this window you can specify a different server instance, for instance
.\MMV if MMV was the name you gave to the SQL 2005 instance. On the
other hand:

>I then launch SQL Server Configuration Manager (SSCM) which contains no
information in any of the items in the tree.

It does not seem that you have any SQL 2005 instances installed at all.

>apparently you have to do this by putting in the CD and re-run the
installation. I did this, but when selecting " Run the SQL Native Client
Installation Wizard" it says that I've got a higher version and cannot
finish. (The reason for this is thatI've installed the SP1). How can I
create a new instance (like, what tool?) so I can connect to one?

If you already have SQL Native Client installed, there is no need to
install it. Just pick "Server components, tools, Books Online and samples"
under the "Install" header.

Pay particular attention when it comes to selecting an instance. If you
select default instance, you will upgrade you SQL 2000 instance. There is
also a button where you can view installed instances.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Aug 13 '06 #5

Erland Sommarskog

Jack (ja**@nospam.com.uk) writes:

When I originally installed SQL 2005 I installed it with the 'default
instance' option. I wrongly assummed that it would have set up a default
'SQL 2005' instance, but what it seemed to have done was take the
EXISTING SQL 2000 instance and treated this as the default. This is why
there were no SQL 2005 instances created.

In that case, the existing SQL 2000 instance would be upgraded, but maybe
you managed to back out of that.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Aug 13 '06 #6