Installing Enterprise version over Standard

We currently are running one instance of SQL Server 2000 Standard with a few databases. We need to upgrade to Enterprise version to use data cubes. Should we be able to install right over the top of our current instance of SQL Server or will we have to
create a new instance?
Thanks in advance for any help.
Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.

Installing Enterprise version over Standard

We currently are running one instance of SQL Server 2000 Standard with a few
databases. We need to upgrade to Enterprise version to use data cubes. Sh
ould we be able to install right over the top of our current instance of SQL
Server or will we have to
create a new instance?
Thanks in advance for any help.Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.|||Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.

Installing Enterprise version over Standard

We currently are running one instance of SQL Server 2000 Standard with a few databases. We need to upgrade to Enterprise version to use data cubes. Should we be able to install right over the top of our current instance of SQL Server or will we have to create a new instance
Thanks in advance for any help.Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft® SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.sql

Installing Developer Edition Management Studio

I'm attempting to upgrade from SQL Express to SQL Developer. I uninstalled completely before loading Dev edition, but I can't seem to install the Management Studio now. Any ideas?

Hello Joe,

Could you please let us know what error you are getting while installing Dev edition?

This will help in narrowing down the cause so that we can resolve it quickly.

Regards,

Rajesh

|||

Actually, I just had to clean up the Windows Installer. Once I removed any references to Express Editions of visual studio and mssql, it worked just fine.

Thanks anyhow.

Installing Developer Edition Management Studio

I'm attempting to upgrade from SQL Express to SQL Developer. I uninstalled completely before loading Dev edition, but I can't seem to install the Management Studio now. Any ideas?

Hello Joe,

Could you please let us know what error you are getting while installing Dev edition?

This will help in narrowing down the cause so that we can resolve it quickly.

Regards,

Rajesh

|||

Actually, I just had to clean up the Windows Installer. Once I removed any references to Express Editions of visual studio and mssql, it worked just fine.

Thanks anyhow.

sql

Installing Developer Edition Management Studio

I'm attempting to upgrade from SQL Express to SQL Developer. I uninstalled completely before loading Dev edition, but I can't seem to install the Management Studio now. Any ideas?

Hello Joe,

Could you please let us know what error you are getting while installing Dev edition?

This will help in narrowing down the cause so that we can resolve it quickly.

Regards,

Rajesh

|||

Actually, I just had to clean up the Windows Installer. Once I removed any references to Express Editions of visual studio and mssql, it worked just fine.

Thanks anyhow.

installing 2005 over 2000

I tried to install 2005 and chose the option to upgrade my existing default
instance. Then it errored out saying, I think, that I need to apply
service packs to my existing 2000 instance.
Why would I need to upgrade something I'm installing over?
Would I be better off just to uninstall 2000, install 2005 and attach all of
my .mdf databases?
Thanks,
TTina,
SQL 2005 will upgrade an existing SQL 2000 instance, but your SQL 2000
instance must be at SP3 or higher. Based on this and your earlier question,
I suggest loading the client tools only for SQL 2005 and doing some reading.
For example, you should really run the upgrade advisor against your existing
database servers to see if there may be any compatibility issues.
The good thing about an upgrade is it keeps all your logins and other
objects in place.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
news:eiTHreqhGHA.4864@.TK2MSFTNGP03.phx.gbl...
>I tried to install 2005 and chose the option to upgrade my existing default
>instance. Then it errored out saying, I think, that I need to apply
>service packs to my existing 2000 instance.
> Why would I need to upgrade something I'm installing over?
> Would I be better off just to uninstall 2000, install 2005 and attach all
> of my .mdf databases?
> Thanks,
> T
>|||I ran the upgrade advisor and it didn't flag any thing about not having the
latest service packs so I thought I was ok. It was only the real install
that flagged that. I guess the advisor doesn't adivse on everything.
T
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23vWfOxqhGHA.3496@.TK2MSFTNGP04.phx.gbl...
> Tina,
> SQL 2005 will upgrade an existing SQL 2000 instance, but your SQL 2000
> instance must be at SP3 or higher. Based on this and your earlier
> question, I suggest loading the client tools only for SQL 2005 and doing
> some reading. For example, you should really run the upgrade advisor
> against your existing database servers to see if there may be any
> compatibility issues.
> The good thing about an upgrade is it keeps all your logins and other
> objects in place.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
> news:eiTHreqhGHA.4864@.TK2MSFTNGP03.phx.gbl...
>>I tried to install 2005 and chose the option to upgrade my existing
>>default instance. Then it errored out saying, I think, that I need to
>>apply service packs to my existing 2000 instance.
>> Why would I need to upgrade something I'm installing over?
>> Would I be better off just to uninstall 2000, install 2005 and attach all
>> of my .mdf databases?
>> Thanks,
>> T
>|||The advisor looks at internal objects in each database. I suppose it should
warn about the server level as well.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
news:%23ymip2yhGHA.1000@.TK2MSFTNGP04.phx.gbl...
>I ran the upgrade advisor and it didn't flag any thing about not having the
>latest service packs so I thought I was ok. It was only the real install
>that flagged that. I guess the advisor doesn't adivse on everything.
> T
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23vWfOxqhGHA.3496@.TK2MSFTNGP04.phx.gbl...
>> Tina,
>> SQL 2005 will upgrade an existing SQL 2000 instance, but your SQL 2000
>> instance must be at SP3 or higher. Based on this and your earlier
>> question, I suggest loading the client tools only for SQL 2005 and doing
>> some reading. For example, you should really run the upgrade advisor
>> against your existing database servers to see if there may be any
>> compatibility issues.
>> The good thing about an upgrade is it keeps all your logins and other
>> objects in place.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>> "Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
>> news:eiTHreqhGHA.4864@.TK2MSFTNGP03.phx.gbl...
>>I tried to install 2005 and chose the option to upgrade my existing
>>default instance. Then it errored out saying, I think, that I need to
>>apply service packs to my existing 2000 instance.
>> Why would I need to upgrade something I'm installing over?
>> Would I be better off just to uninstall 2000, install 2005 and attach
>> all of my .mdf databases?
>> Thanks,
>> T
>>
>

installing 2005 over 2000

I tried to install 2005 and chose the option to upgrade my existing default
instance. Then it errored out saying, I think, that I need to apply
service packs to my existing 2000 instance.
Why would I need to upgrade something I'm installing over?
Would I be better off just to uninstall 2000, install 2005 and attach all of
my .mdf databases?
Thanks,
TTina,
SQL 2005 will upgrade an existing SQL 2000 instance, but your SQL 2000
instance must be at SP3 or higher. Based on this and your earlier question,
I suggest loading the client tools only for SQL 2005 and doing some reading.
For example, you should really run the upgrade advisor against your existing
database servers to see if there may be any compatibility issues.
The good thing about an upgrade is it keeps all your logins and other
objects in place.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
news:eiTHreqhGHA.4864@.TK2MSFTNGP03.phx.gbl...
>I tried to install 2005 and chose the option to upgrade my existing default
>instance. Then it errored out saying, I think, that I need to apply
>service packs to my existing 2000 instance.
> Why would I need to upgrade something I'm installing over?
> Would I be better off just to uninstall 2000, install 2005 and attach all
> of my .mdf databases?
> Thanks,
> T
>|||I ran the upgrade advisor and it didn't flag any thing about not having the
latest service packs so I thought I was ok. It was only the real install
that flagged that. I guess the advisor doesn't adivse on everything.
T
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23vWfOxqhGHA.3496@.TK2MSFTNGP04.phx.gbl...
> Tina,
> SQL 2005 will upgrade an existing SQL 2000 instance, but your SQL 2000
> instance must be at SP3 or higher. Based on this and your earlier
> question, I suggest loading the client tools only for SQL 2005 and doing
> some reading. For example, you should really run the upgrade advisor
> against your existing database servers to see if there may be any
> compatibility issues.
> The good thing about an upgrade is it keeps all your logins and other
> objects in place.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
> news:eiTHreqhGHA.4864@.TK2MSFTNGP03.phx.gbl...
>|||The advisor looks at internal objects in each database. I suppose it should
warn about the server level as well.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
news:%23ymip2yhGHA.1000@.TK2MSFTNGP04.phx.gbl...
>I ran the upgrade advisor and it didn't flag any thing about not having the
>latest service packs so I thought I was ok. It was only the real install
>that flagged that. I guess the advisor doesn't adivse on everything.
> T
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23vWfOxqhGHA.3496@.TK2MSFTNGP04.phx.gbl...
>

installation fails on xp home - failed to configure server

Hi,
First I attemtped to upgrade MSDE to sp4, and I got the error
"This product is not installed",
So I removed the installation of MSDE and just installed sp4 directly. But
when I do, I get the error
"Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (A4!4C) [12:01:18:241]: Product: Microsoft SQL Server Desktop Engine
(VLM) -- Setup failed to configure the server. Refer to the server error
logs and setup error logs for more information."
The only other line in the log that metions a failure is
Setting SqlEdition property failed
The installer then backs everthing out and removes the service. The service
was already installed and running at that point.
I am using SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE to install,
Thanks,
Brian
hi Brian,
msnews.microsoft.com wrote:
> Hi,
> First I attemtped to upgrade MSDE to sp4, and I got the error
> "This product is not installed",
> So I removed the installation of MSDE and just installed sp4
> directly. But when I do, I get the error
> "Setup failed to configure the server. Refer to the server error logs
> and setup error logs for more information.
> MSI (s) (A4!4C) [12:01:18:241]: Product: Microsoft SQL Server Desktop
> Engine (VLM) -- Setup failed to configure the server. Refer to the
> server error logs and setup error logs for more information."
> The only other line in the log that metions a failure is
> Setting SqlEdition property failed
> The installer then backs everthing out and removes the service. The
> service was already installed and running at that point.
> I am using SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE to install,
this usually means you did not comletely uninstall MSDE (not your fault,
just MSDE fault :D)
I succesfully cleared my registry and file system following
http://support.microsoft.com/default...b;en-us;290991 KB article
adiveces but the Windows Installer entries, that can be cleared using the
Windows Installer SDK tool Msizap.exe as per
http://support.microsoft.com/default...b;en-us;320873 (never tried)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Got it fixed.
To get it to work I did the following:
1. Intalled a default instance. I had removed it as well. That worked.
2. re-registering sqldmo.dll. I did this because DbaMgr got an automation
error when connecting to the default instance
3. Installed the named instance I wanted. This time it worked.
Notes:
The error I was getting was
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error.
Check your network documentation.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()).
Things learned along the way:
1. If the install fails, then enable verbose logging with /L*v
C:\MSDELog.log. Look in the log when its finished for what failed. When you
get the error message box, LEAVE IT THERE, and go look at the log. The last
thing it did is the last line.
2. If you get the error "Unable to configure server", then look in the file
cnfgsvr.out. It will be in C:\Program files\Microsoft SQL
Server\MSSQL$<instancename>\Inatall (assuming drive c)
3. To clean manully to get the installer to resintall completely if a
partial install is left on the system:
- Run Windows Installer SDK tool Msizap.exe as per
http://support.microsoft.com/default...b;en-us;320873
The command is MSIZAP.EXE" T {product code}. The product code can be
found in the install log (C:\MSDELog.log in the example above). The product
code for MDSE service pack 4 was
{E09B48B5-E141-427A-AB0C-D3605127224A} so I ran
MSIZAP.EXE" T {E09B48B5-E141-427A-AB0C-D3605127224A}
- Manually delete the folder C:\Program Files\Microsoft SQL Server\MSSQL
or C:\Program Files\Microsoft SQL Server\MSSQL$<instancename>. Make sure you
look at cnfgsvr.out first if you need too!
Brian
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3s9k91Fn804jU1@.individual.net...
> hi Brian,
> msnews.microsoft.com wrote:
> this usually means you did not comletely uninstall MSDE (not your fault,
> just MSDE fault :D)
> I succesfully cleared my registry and file system following
> http://support.microsoft.com/default...b;en-us;290991 KB article
> adiveces but the Windows Installer entries, that can be cleared using the
> Windows Installer SDK tool Msizap.exe as per
> http://support.microsoft.com/default...b;en-us;320873 (never
> tried)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>