EdVassie (1/21/2009)

---

. . . doing an in-place upgrade from SQL 2000 to SQL 2005 is a risky business. I have tried this on two supposedly identical servers and...

(LOL) That's good -- because it's the only game plan we have at this point . . .

Thanks much (!)

Matt Miller (1/19/2009)

---

Perry Whittle (1/19/2009)

---

Matt, it would seem he has a mixture of sql2000 instances, 2 of the instances are the MSDE which SBS installs. The other 2 seem to...

Hi Perry . . .

(1) We backed out the upgrade we tried over the weekend . . . and will try again next weekend.

(2) Right now, we're assuming that the...

When I connect to any of the 4 instances via SSMS . . . the @@version comes back as:

Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May...

(1) Still not sure that SS2005 was installed sucessfully during the upgrade process.

(2) When I go into the SQL Server 2005 Surface Area Configuration, for example, the database engine is...

Okay -- thanks.

Let me see what happens when I try to connect to each of the instances . . .

installed instances:

SBSMONITORING

MSSQLSERVER

COW0

MSSQL$COW0

Four installed instances. I'm connecting to COW0 -- which comes up fine as far as it goes, but it's 8.0 . . .

I'm accessing COW0 with Management Studio -- that's got our production database and it's okay. It's just coming up as 2000.

Apparently . . . four instances of MSSQLSERVER and 4 corresponding SQLAgents.

But they're all SS2000, as best I can figure . . .

Right -- what does this tell us please?