Is SQL server not installed with VS2005

[Developer]

Hello All,
i have recently installed VS2005 and was trying to install SQL sever
2000.
I have Win XP' SP2. But when I tried installing, it only installed
client tools and not the database.
Can anyone please help me with this as I want to install SQL server and
also wouold be grateful, if you can suggest me any workaround to
dealwith this problem.(Like should I install any new OS etc).

Any help would be appreciated.

Thanks and Regards,
Deo

 

[Juan T. Llibre]

You can't install SQL Server 2000 on Windows XP.
You *can* install MSDE 2000 or SQL Server 2005 Express.

http://www.microsoft.com/sql/prodinfo/previousversions/msde/prodinfo.mspx

http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx

 

[Marina Levit [MVP]]

I have SQL Server 2000 running right now on my Windows XP Pro machine, and
have had it for several years.

 

[Mark Rae]

You can't install SQL Server 2000 on Windows XP.

??? Of course you can.

 

[SRussell]

You can't install SQL Server 2000 on Windows XP.
You *can* install MSDE 2000 or SQL Server 2005 Express.

http://www.microsoft.com/sql/prodinfo/previousversions/msde/prodinfo.mspx

http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx

Depends on the VERSION of SQL Server 2000. Enterprise demands a server,
Developer will install just fine on a laptop.

 

[sloan]

As previously illuded to, you can install msde or sql server developers
edition.
If you don't have (in hand) the developers edition of 2000, then msde is
good soluton.
Its free, has the same engine as 2000, but includes a few artificially
imposed "govenors" so that it works good, but doesn't scale up to be able to
run amazon.com or something.
I refer to it as "sql server 2000 lite".

Go here:
http://sholliday.spaces.live.com/blog/ 12/16/2005 How to Install
MSDE (Sql Server 2000 Desktop)


You best combination is to keep your (legal) copies of the client tools, and
install msde. ...........
From query analyser and enterprise studio's point of view, the msde install
is just another sql server 2000 database engine.

The only thing that msde doesn't have , that is kinda of a pain , is the
abilty to monitor jobs. Sql Server Agent is the lacking feature.

 

[Juan T. Llibre]

Incorrect.

http://www.microsoft.com/sql/prodinfo/previousversions/system-requirements.mspx

SQL Server 2000 Enterprise Edition and Standard Edition can run on the following operating systems:

Windows Server 2003 R2
Windows Server 2003, Standard Edition1
Windows Server 2003, Enterprise Edition2
Windows Server 2003, Datacenter Edition3
Windows® 2000 Server
Windows 2000 Advanced Server
Windows 2000 Datacenter Server

SQL Server 2000 Evaluation Edition and Developer Edition
and Workgroup Edition can run on the following operating systems:

Operating systems listed above for Enterprise and Standard Editions
Windows XP Professional
Windows XP Home Edition
Windows 2000 Professional

SQL Server 2000 Personal Edition4 and SQL Server 2000
Desktop Engine (MSDE) can run on the following operating systems:

Operating systems listed above for Enterprise, Standard, Evaluation, and Developer Editions
Windows Server 2003, Web Edition5 (MSDE only)
Windows 98
Windows Millennium Edition (Windows Me)

If you are running Windows XP, you are running either
SQL Server 2000 Evaluation Edition or Developer Edition or Workgroup Edition.

Let me repeat :

You *cannot* run SQL Server 2000 Enterprise Edition nor the Standard Edition on XP.
*Those* are what the name "SQL Server 2000" refers to.

The Developer, Workgroup, and Personal editions *cannot* do what SQL Server 2000 does.

 

[Juan T. Llibre]

Incorrect.

http://www.microsoft.com/sql/prodinfo/previousversions/system-requirements.mspx

SQL Server 2000 Enterprise Edition and Standard Edition can run on the following operating systems:

Windows Server 2003 R2
Windows Server 2003, Standard Edition1
Windows Server 2003, Enterprise Edition2
Windows Server 2003, Datacenter Edition3
Windows® 2000 Server
Windows 2000 Advanced Server
Windows 2000 Datacenter Server

SQL Server 2000 Evaluation Edition and Developer Edition
and Workgroup Edition can run on the following operating systems:

Operating systems listed above for Enterprise and Standard Editions
Windows XP Professional
Windows XP Home Edition
Windows 2000 Professional

SQL Server 2000 Personal Edition and SQL Server 2000
Desktop Engine (MSDE) can run on the following operating systems:

Operating systems listed above for Enterprise, Standard, Evaluation, and Developer Editions
Windows Server 2003, Web Edition5 (MSDE only)
Windows 98
Windows Millennium Edition (Windows Me)

If you are running Windows XP, you are running either the Developer Edition
or the Workgroup Edition or the Personal Edition.

Let me repeat :
You *cannot* run SQL Server 2000 Enterprise Edition nor the Standard Edition on XP.

*Those* are what the name "SQL Server 2000" refers to.
The Developer, Workgroup, and Personal editions *cannot* do what SQL Server 2000 Server does.

 

[Juan T. Llibre]

Sure, but the "Developer edition" is *not* "SQL Server 2000".
It's a Developer edition...with a lot of missing features.

The proper nomenclature assures us that we are on the same page.

You *cannot* speak of the Developer edition being "SQL Server 2000".
It's not.

 

[Marina Levit [MVP]]

No, it is not incorrect.

Just because it is the developer edition, doesn't mean it's not SQL Server
2000. It just means it is SQL Server 2000 developer edition. And yes,
different editions may have different capabilities, but it is still called
and referred to as 'SQL Server 2000'. Otherwise, what would you call it -
the developer edition of what? The product has to have a name, and that name
is 'SQL Server 2000'.

Just like there are different editions of Visual Studio .NET - and they all
have different capabilities, but they are all still Visual Studio .NET. Just
different editions of it.

 

[Juan T. Llibre]

re:

and referred to as 'SQL Server 2000'. Otherwise, what would you call it - the developer edition
of what?

The "developer edition" of "SQL Server", of course.

"SQL Server 2000" is a product.
"SQL Server 2000 Developer Edition" is a different product.

You should call each product by its (proper) name.

re:

Just like there are different editions of Visual Studio .NET - and they all have different
capabilities, but they are all still Visual Studio .NET. Just different editions of it.

I would *never* call any of the Express Editions "Visual Studio 2005".
The proper way to refer to the Express editions is to include the "Express" moniker.

The same for SQL Server and its editions.

No, it is not incorrect.

Just because it is the developer edition, doesn't mean it's not SQL Server 2000. It just means it
is SQL Server 2000 developer edition. And yes, different editions may have different
capabilities, but it is still called and referred to as 'SQL Server 2000'. Otherwise, what would
you call it - the developer edition of what? The product has to have a name, and that name is 'SQL
Server 2000'.

Just like there are different editions of Visual Studio .NET - and they all have different
capabilities, but they are all still Visual Studio .NET. Just different editions of it.

 

[Marina Levit [MVP]]

"The developer edition of SQL Server" does not refer to a particular
version. I mean, when was this developer edition released? Could be any
time, since there is no version number tied to it. Microsoft always refers
to it with the version number.

If you ask someone who has this installed on their machine, every single one
will tell you they have SQL Server 2000 running on their machine. I know
this, because this is what developers answer me, and what I answer
developers. Because in fact, it is the fact that it is the 2000 edition
that people care about. The fact that it happens to be the developer
edition is actually irrelevant to developers, as they just want to have a
local database to run against. Developers just don't care whether or not
they have the full fledged SQL Server installed.

But they do care if it's 2000 vs 2005, vs another older version, as that
actually has an impact as to how they write their code.

Lastly, if you do "select @@version", you get:

Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation Personal Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)

Notice that MS considers this 'Microsoft SQL Server 2000", and mention this
in the name.

 

[Juan T. Llibre]

re:

Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15 Copyright (c) 1988-2003
Microsoft Corporation Personal Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
Notice that MS considers this 'Microsoft SQL Server 2000", and mention this in the name.

I suppose that calling it a "Personal Edition" means diddly,
and that it can do everything that the real "SQL Server 2000" does.

Does it ?

re:

Developers just don't care whether or not they have the full fledged SQL Server installed.

Ah, you do admit that a "full fledged SQL Server" exists ?
So, the version you refer to is *less* than a "full fledged SQL Server".

Thank you.

re:

Personal Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

You need to upgrade that version, btw.
You're at risk if you're not running SP4.

SQL Server SP3 has been available since January, 2003.
SQL Server SP4 has been available since May, 2005.

 

[Marina Levit [MVP]]

Well, there is "enterprise edition". There are also other editions. They
are all referred to by Microsoft as "Microsoft SQL Server 2000" followed by
the edition name.

As in: http://www.microsoft.com/sql/editions/developer/default.mspx.

Notice in this case it is 'SQL Server 2005 Developer edition" in the banner.
It's not just 'Developer Edition' of some unnamed product.

It is not that one is SQL Server 2000, and the others are just scraps of
something else. All of those editions are SQL Server 2000 - and each is
just a particular edition of it.

So when you tell someone they can't have SQL Server 2000 on their machine,
that implies that none of the editions can be installed, which is just plain
misinformation.

It's like buying a car - there are usually several different editions of
each model. But they are all considered to be that model, even though some
are luxury, some have four wheel drive, and so on. They all have the same
basics that identify the car as that particular model.

Same goes for SQL Server 2000 and its various flavors.

 

[Juan T. Llibre]

Tell you what, Marina :

You tell your customers that they have SQL Server 2000 installed
when what they actually have is a Developer edition.

They may think you're a wizard for saving them so much in license costs.

;-)

I like to call products by their proper name.
It saves a lot of confusion and misunderstanding.

Look at the question the OP asked in his first post:

i have recently installed VS2005 and was trying to install SQL server 2000.
I have Win XP' SP2. But when I tried installing, it only installed client tools and not the
database.

Now, tell him that he can run SQL Server 2000 on Windows XP.
The obvious answer is that he can't run SQL Server 2000 on XP.

You can install SQL Server *Developer Edition* on XP, but you *cannot* install
SQL Server 2000 on XP, except for the Evaluation Edition which is a PITA,
because it runs out after 120 days.

When you attempt to install SQL Server 2000 on XP,
all you get installed are the client tools, as our OP discovered.

The recommendation in his case is to install the SQL Server 2000 Desktop Engine,
( MSDE 2000 ) or upgrade to SQL Server 2005 Express, for development purposes.

A good guide to the differences between the different editions of SQL Server 2000 is at:
http://72.14.209.104/search?q=cache...bb6e6-9d97-4a5d-be8d-508256ae4045/ChoosEd.doc