I first tried to upgrade the default instance of our SQL Server 2005 SP2 from
the Standard Edition to Enterprise Edition from the CD and I got the
following message:

“Edition Change Check (Warning): To change an existing instance of Microsoft
SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL
Server 2005 Setup from the command prompt and include the SKUUPGRADE=1
parameter�

Then I run the following command from DOS prompt [Ref:
http://msdn.microsoft.com/en-us/library/ms144259.aspx]:

start /wait setup.exe ADDLOCAL=SQL_Engine INSTANCENAME=MSSQLSERVER
UPGRADE=SQL_Engine SKUUPGRADE=1 /qb

The above command ran only for less than TWO minutes. I was a little
suspicious that the upgrade would be completed within two minutes. So, I ran
the following query on the query analyzer:

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'),
SERVERPROPERTY ('edition')

And the result of the above query was as follows:

9.00.3042.00 SP2 Enterprise Edition

But according to MSDN [Ref:
http://msdn.microsoft.com/en-us/library/ms144259.aspx]:

“If you use the SKUUPGRADE parameter, Setup will remove all hotfix and
service pack updates from the SQL Server instance being upgraded. Once the
edition upgrade is complete, you must reapply all hotfix and service pack
updates.�

My Question is: How come upgrade was completed within two minutes and that
it did not remove SP2. Is there any way I can verify from any feature that
Enterprise edition has but Standard edition does not? Or any other way of
verifying that indeed we have enterprise edition running? We have only
Database Engine and SQL Server Reporting Services installed.

Thank You.

Well, It usually takes more than 2 minutes =)

I guess your Upgrade attempt failed somehow and you missed it. Because if
you had upgraded your SQL Server Standard Edition instance to Enterprise
Edition, then you'd really lose all of the service packs and updates you
performed against your SQL Server instance. It would get back to version
1399 which is the RTM.

You might be connected to another SQL Server Enterprise Edition instance and
ran the version commands against it.

I suggest you to go to Configuration Manager and check out your installed
SQL Server instances. Ensure how many instance you have installed on your
system and what they are. Connect each of them one by one using SSMS and
check them out.

--
Ekrem Önsoy



"Nam" <Nam@discussions.microsoft.com> wrote in message
news:E5F176A2-5879-4203-81DF-A7A23BA6D5AB@microsoft.com...
>I first tried to upgrade the default instance of our SQL Server 2005 SP2
>from
> the Standard Edition to Enterprise Edition from the CD and I got the
> following message:
>
> “Edition Change Check (Warning): To change an existing instance of
> Microsoft
> SQL Server 2005 to a different edition of SQL Server 2005, you must run
> SQL
> Server 2005 Setup from the command prompt and include the SKUUPGRADE=1
> parameter�
>
> Then I run the following command from DOS prompt [Ref:
> http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
>
> start /wait setup.exe ADDLOCAL=SQL_Engine INSTANCENAME=MSSQLSERVER
> UPGRADE=SQL_Engine SKUUPGRADE=1 /qb
>
> The above command ran only for less than TWO minutes. I was a little
> suspicious that the upgrade would be completed within two minutes. So, I
> ran
> the following query on the query analyzer:
>
> SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'),
> SERVERPROPERTY ('edition')
>
> And the result of the above query was as follows:
>
> 9.00.3042.00 SP2 Enterprise Edition
>
> But according to MSDN [Ref:
> http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
>
> “If you use the SKUUPGRADE parameter, Setup will remove all hotfix and
> service pack updates from the SQL Server instance being upgraded. Once the
> edition upgrade is complete, you must reapply all hotfix and service pack
> updates.�
>
> My Question is: How come upgrade was completed within two minutes and that
> it did not remove SP2. Is there any way I can verify from any feature that
> Enterprise edition has but Standard edition does not? Or any other way of
> verifying that indeed we have enterprise edition running? We have only
> Database Engine and SQL Server Reporting Services installed.
>
> Thank You.

> “If you use the SKUUPGRADE parameter, Setup will remove all hotfix and
> service pack updates from the SQL Server instance being upgraded. Once the
> edition upgrade is complete, you must reapply all hotfix and service pack
> updates.�
>
> My Question is: How come upgrade was completed within two minutes and that
> it did not remove SP2.

Note that the article does not say that SP2 is removed by the upgrade. It
states that it needs to be reapplied after the upgrade.

> Is there any way I can verify from any feature that
> Enterprise edition has but Standard edition does not? Or any other way of
> verifying that indeed we have enterprise edition running? We have only
> Database Engine and SQL Server Reporting Services installed.

Partitioning is a feature available in EE and DE only so I would expect the
following statement to fail. I don't have a standard instance to test this
on, though.

CREATE PARTITION FUNCTION PF_Test(int)
AS RANGE FOR VALUES();


--
Hope this s.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"Nam" <Nam@discussions.microsoft.com> wrote in message
news:E5F176A2-5879-4203-81DF-A7A23BA6D5AB@microsoft.com...
>I first tried to upgrade the default instance of our SQL Server 2005 SP2
>from
> the Standard Edition to Enterprise Edition from the CD and I got the
> following message:
>
> “Edition Change Check (Warning): To change an existing instance of
> Microsoft
> SQL Server 2005 to a different edition of SQL Server 2005, you must run
> SQL
> Server 2005 Setup from the command prompt and include the SKUUPGRADE=1
> parameter�
>
> Then I run the following command from DOS prompt [Ref:
> http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
>
> start /wait setup.exe ADDLOCAL=SQL_Engine INSTANCENAME=MSSQLSERVER
> UPGRADE=SQL_Engine SKUUPGRADE=1 /qb
>
> The above command ran only for less than TWO minutes. I was a little
> suspicious that the upgrade would be completed within two minutes. So, I
> ran
> the following query on the query analyzer:
>
> SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'),
> SERVERPROPERTY ('edition')
>
> And the result of the above query was as follows:
>
> 9.00.3042.00 SP2 Enterprise Edition
>
> But according to MSDN [Ref:
> http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
>
> “If you use the SKUUPGRADE parameter, Setup will remove all hotfix and
> service pack updates from the SQL Server instance being upgraded. Once the
> edition upgrade is complete, you must reapply all hotfix and service pack
> updates.�
>
> My Question is: How come upgrade was completed within two minutes and that
> it did not remove SP2. Is there any way I can verify from any feature that
> Enterprise edition has but Standard edition does not? Or any other way of
> verifying that indeed we have enterprise edition running? We have only
> Database Engine and SQL Server Reporting Services installed.
>
> Thank You.

Thank you so much for your . I ran your SQL query on our Standard Edition
and got the following message:

“Msg 7736, Level 16, State 1, Line 2
Partition function can only be created in Enterprise edition of SQL Server.
Only Enterprise edition of SQL Server supports partitioning.�

Whereas, the query ran successfully on the server in question (that I
upgraded to Enterprise Edition).

The mystery remains as to how the command line prompt upgraded the Server to
EE within less than two minutes and why SP2 was not removed whereas the MSDN
article clearly states the following: “If you use the SKUUPGRADE parameter,
Setup will REMOVE all hotfix and service pack updates from the SQL Server
instance being upgraded�

Was there anything got missed in my upgrade process and is there anything
else I need to do in order to make sure we are working on a 100% Enterprise
Edition and to avoid any problems in future when all the applications
connected to SQL Server are already installed and running?

We have only two machines (Win 2003) both had only one instance of SQL 2005
Standard Edition one of which we upgraded to Enterprise Edition. Both
instances are default instances.

Thank you.....

"Dan Guzman" wrote:

> > “If you use the SKUUPGRADE parameter, Setup will remove all hotfix and
> > service pack updates from the SQL Server instance being upgraded. Once the
> > edition upgrade is complete, you must reapply all hotfix and service pack
> > updates.�
> >
> > My Question is: How come upgrade was completed within two minutes and that
> > it did not remove SP2.
>
> Note that the article does not say that SP2 is removed by the upgrade. It
> states that it needs to be reapplied after the upgrade.
>
> > Is there any way I can verify from any feature that
> > Enterprise edition has but Standard edition does not? Or any other way of
> > verifying that indeed we have enterprise edition running? We have only
> > Database Engine and SQL Server Reporting Services installed.
>
> Partitioning is a feature available in EE and DE only so I would expect the
> following statement to fail. I don't have a standard instance to test this
> on, though.
>
> CREATE PARTITION FUNCTION PF_Test(int)
> AS RANGE FOR VALUES();
>
>
> --
> Hope this s.
>
> Dan Guzman
> SQL Server MVP
> http://weblogs.sqlteam.com/dang/
>
> "Nam" <Nam@discussions.microsoft.com> wrote in message
> news:E5F176A2-5879-4203-81DF-A7A23BA6D5AB@microsoft.com...
> >I first tried to upgrade the default instance of our SQL Server 2005 SP2
> >from
> > the Standard Edition to Enterprise Edition from the CD and I got the
> > following message:
> >
> > “Edition Change Check (Warning): To change an existing instance of
> > Microsoft
> > SQL Server 2005 to a different edition of SQL Server 2005, you must run
> > SQL
> > Server 2005 Setup from the command prompt and include the SKUUPGRADE=1
> > parameter�
> >
> > Then I run the following command from DOS prompt [Ref:
> > http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
> >
> > start /wait setup.exe ADDLOCAL=SQL_Engine INSTANCENAME=MSSQLSERVER
> > UPGRADE=SQL_Engine SKUUPGRADE=1 /qb
> >
> > The above command ran only for less than TWO minutes. I was a little
> > suspicious that the upgrade would be completed within two minutes. So, I
> > ran
> > the following query on the query analyzer:
> >
> > SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'),
> > SERVERPROPERTY ('edition')
> >
> > And the result of the above query was as follows:
> >
> > 9.00.3042.00 SP2 Enterprise Edition
> >
> > But according to MSDN [Ref:
> > http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
> >
> > “If you use the SKUUPGRADE parameter, Setup will remove all hotfix and
> > service pack updates from the SQL Server instance being upgraded. Once the
> > edition upgrade is complete, you must reapply all hotfix and service pack
> > updates.�
> >
> > My Question is: How come upgrade was completed within two minutes and that
> > it did not remove SP2. Is there any way I can verify from any feature that
> > Enterprise edition has but Standard edition does not? Or any other way of
> > verifying that indeed we have enterprise edition running? We have only
> > Database Engine and SQL Server Reporting Services installed.
> >
> > Thank You.
>

Hi, Nam.

It's been a long while since I did an SKUUPRGRADE so I tested one one
against a SE SP2 test vpc machine. After the she successful upgrade,

SELECT
SERVERPROPERTY('productversion'),
SERVERPROPERTY ('productlevel'),
SERVERPROPERTY ('edition')

Returns:

9.00.1399.06 RTM Enterprise Edition

and a CREATE PARTITION FUNCTION succeeded. After the SP2 install, the query
returned:

9.00.3042.00 SP2 Enterprise Edition

Have you checked the setup log files (in C:\Program Files\Microsoft SQL
Server\90\Setup Bootstrap\LOG\Files) for errors?

--
Hope this s.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"Nam" <Nam@discussions.microsoft.com> wrote in message
news:9AA270EB-7452-46BF-814A-8BCF07B6AF5C@microsoft.com...
> Thank you so much for your . I ran your SQL query on our Standard
> Edition
> and got the following message:
>
> “Msg 7736, Level 16, State 1, Line 2
> Partition function can only be created in Enterprise edition of SQL
> Server.
> Only Enterprise edition of SQL Server supports partitioning.�
>
> Whereas, the query ran successfully on the server in question (that I
> upgraded to Enterprise Edition).
>
> The mystery remains as to how the command line prompt upgraded the Server
> to
> EE within less than two minutes and why SP2 was not removed whereas the
> MSDN
> article clearly states the following: “If you use the SKUUPGRADE
> parameter,
> Setup will REMOVE all hotfix and service pack updates from the SQL Server
> instance being upgraded�
>
> Was there anything got missed in my upgrade process and is there anything
> else I need to do in order to make sure we are working on a 100%
> Enterprise
> Edition and to avoid any problems in future when all the applications
> connected to SQL Server are already installed and running?
>
> We have only two machines (Win 2003) both had only one instance of SQL
> 2005
> Standard Edition one of which we upgraded to Enterprise Edition. Both
> instances are default instances.
>
> Thank you.....
>
> "Dan Guzman" wrote:
>
>> > “If you use the SKUUPGRADE parameter, Setup will remove all hotfix and
>> > service pack updates from the SQL Server instance being upgraded. Once
>> > the
>> > edition upgrade is complete, you must reapply all hotfix and service
>> > pack
>> > updates.�
>> >
>> > My Question is: How come upgrade was completed within two minutes and
>> > that
>> > it did not remove SP2.
>>
>> Note that the article does not say that SP2 is removed by the upgrade.
>> It
>> states that it needs to be reapplied after the upgrade.
>>
>> > Is there any way I can verify from any feature that
>> > Enterprise edition has but Standard edition does not? Or any other way
>> > of
>> > verifying that indeed we have enterprise edition running? We have only
>> > Database Engine and SQL Server Reporting Services installed.
>>
>> Partitioning is a feature available in EE and DE only so I would expect
>> the
>> following statement to fail. I don't have a standard instance to test
>> this
>> on, though.
>>
>> CREATE PARTITION FUNCTION PF_Test(int)
>> AS RANGE FOR VALUES();
>>
>>
>> --
>> Hope this s.
>>
>> Dan Guzman
>> SQL Server MVP
>> http://weblogs.sqlteam.com/dang/
>>
>> "Nam" <Nam@discussions.microsoft.com> wrote in message
>> news:E5F176A2-5879-4203-81DF-A7A23BA6D5AB@microsoft.com...
>> >I first tried to upgrade the default instance of our SQL Server 2005 SP2
>> >from
>> > the Standard Edition to Enterprise Edition from the CD and I got the
>> > following message:
>> >
>> > “Edition Change Check (Warning): To change an existing instance of
>> > Microsoft
>> > SQL Server 2005 to a different edition of SQL Server 2005, you must run
>> > SQL
>> > Server 2005 Setup from the command prompt and include the SKUUPGRADE=1
>> > parameter�
>> >
>> > Then I run the following command from DOS prompt [Ref:
>> > http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
>> >
>> > start /wait setup.exe ADDLOCAL=SQL_Engine INSTANCENAME=MSSQLSERVER
>> > UPGRADE=SQL_Engine SKUUPGRADE=1 /qb
>> >
>> > The above command ran only for less than TWO minutes. I was a little
>> > suspicious that the upgrade would be completed within two minutes. So,
>> > I
>> > ran
>> > the following query on the query analyzer:
>> >
>> > SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY
>> > ('productlevel'),
>> > SERVERPROPERTY ('edition')
>> >
>> > And the result of the above query was as follows:
>> >
>> > 9.00.3042.00 SP2 Enterprise Edition
>> >
>> > But according to MSDN [Ref:
>> > http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
>> >
>> > “If you use the SKUUPGRADE parameter, Setup will remove all hotfix and
>> > service pack updates from the SQL Server instance being upgraded. Once
>> > the
>> > edition upgrade is complete, you must reapply all hotfix and service
>> > pack
>> > updates.�
>> >
>> > My Question is: How come upgrade was completed within two minutes and
>> > that
>> > it did not remove SP2. Is there any way I can verify from any feature
>> > that
>> > Enterprise edition has but Standard edition does not? Or any other way
>> > of
>> > verifying that indeed we have enterprise edition running? We have only
>> > Database Engine and SQL Server Reporting Services installed.
>> >
>> > Thank You.
>>

Dan,

Thank you for trying to . I found the following four files in C:\Program
Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files that were created at
the time of upgrade process:

SQLSetup0003_MYMACHINENAME_Support.log
SQLSetup0003_MYMACHINENAME_SCC.log
SQLSetup0003_MYMACHINENAME_Core(Patched).log
SQLSetup0003_MYMACHINENAME_Core.log

Is there anything specific I should look into the above files. Following is
all the content from the last of the above files:

Microsoft SQL Server 2005 Setup beginning at Thu May 01 18:31:19 2008
Process ID : 5460
F:\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2008/4/1 18:31:15
Complete: LoadResourcesAction at: 2008/4/1 18:31:15, returned true
Running: ParseBootstrapOptionsAction at: 2008/4/1 18:31:15
Loaded DLL:F:\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2008/4/1 18:31:18, returned true
Running: ValidateWinNTAction at: 2008/4/1 18:31:18
Complete: ValidateWinNTAction at: 2008/4/1 18:31:18, returned true
Running: ValidateMinOSAction at: 2008/4/1 18:31:18
Complete: ValidateMinOSAction at: 2008/4/1 18:31:18, returned true
Running: PerformSCCAction at: 2008/4/1 18:31:18
Complete: PerformSCCAction at: 2008/4/1 18:31:19, returned true
Running: ActivateLoggingAction at: 2008/4/1 18:31:19
Complete: ActivateLoggingAction at: 2008/4/1 18:31:20, returned true
Running: DetectPatchedBootstrapAction at: 2008/4/1 18:31:20
Complete: DetectPatchedBootstrapAction at: 2008/4/1 18:31:21, returned true
Running: LaunchPatchedBootstrapAction at: 2008/4/1 18:31:24
Error: Action "LaunchPatchedBootstrapAction" threw an exception during
execution. Error information reported during run:
"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe"
finished and returned: 0
Aborting queue processing as nested installer has completed
Message pump returning: 0

Thank you.......


"Dan Guzman" wrote:

> Hi, Nam.
>
> It's been a long while since I did an SKUUPRGRADE so I tested one one
> against a SE SP2 test vpc machine. After the she successful upgrade,
>
> SELECT
> SERVERPROPERTY('productversion'),
> SERVERPROPERTY ('productlevel'),
> SERVERPROPERTY ('edition')
>
> Returns:
>
> 9.00.1399.06 RTM Enterprise Edition
>
> and a CREATE PARTITION FUNCTION succeeded. After the SP2 install, the query
> returned:
>
> 9.00.3042.00 SP2 Enterprise Edition
>
> Have you checked the setup log files (in C:\Program Files\Microsoft SQL
> Server\90\Setup Bootstrap\LOG\Files) for errors?
>
> --
> Hope this s.
>
> Dan Guzman
> SQL Server MVP
> http://weblogs.sqlteam.com/dang/
>
> "Nam" <Nam@discussions.microsoft.com> wrote in message
> news:9AA270EB-7452-46BF-814A-8BCF07B6AF5C@microsoft.com...
> > Thank you so much for your . I ran your SQL query on our Standard
> > Edition
> > and got the following message:
> >
> > “Msg 7736, Level 16, State 1, Line 2
> > Partition function can only be created in Enterprise edition of SQL
> > Server.
> > Only Enterprise edition of SQL Server supports partitioning.�
> >
> > Whereas, the query ran successfully on the server in question (that I
> > upgraded to Enterprise Edition).
> >
> > The mystery remains as to how the command line prompt upgraded the Server
> > to
> > EE within less than two minutes and why SP2 was not removed whereas the
> > MSDN
> > article clearly states the following: “If you use the SKUUPGRADE
> > parameter,
> > Setup will REMOVE all hotfix and service pack updates from the SQL Server
> > instance being upgraded�
> >
> > Was there anything got missed in my upgrade process and is there anything
> > else I need to do in order to make sure we are working on a 100%
> > Enterprise
> > Edition and to avoid any problems in future when all the applications
> > connected to SQL Server are already installed and running?
> >
> > We have only two machines (Win 2003) both had only one instance of SQL
> > 2005
> > Standard Edition one of which we upgraded to Enterprise Edition. Both
> > instances are default instances.
> >
> > Thank you.....
> >
> > "Dan Guzman" wrote:
> >
> >> > “If you use the SKUUPGRADE parameter, Setup will remove all hotfix and
> >> > service pack updates from the SQL Server instance being upgraded. Once
> >> > the
> >> > edition upgrade is complete, you must reapply all hotfix and service
> >> > pack
> >> > updates.�
> >> >
> >> > My Question is: How come upgrade was completed within two minutes and
> >> > that
> >> > it did not remove SP2.
> >>
> >> Note that the article does not say that SP2 is removed by the upgrade.
> >> It
> >> states that it needs to be reapplied after the upgrade.
> >>
> >> > Is there any way I can verify from any feature that
> >> > Enterprise edition has but Standard edition does not? Or any other way
> >> > of
> >> > verifying that indeed we have enterprise edition running? We have only
> >> > Database Engine and SQL Server Reporting Services installed.
> >>
> >> Partitioning is a feature available in EE and DE only so I would expect
> >> the
> >> following statement to fail. I don't have a standard instance to test
> >> this
> >> on, though.
> >>
> >> CREATE PARTITION FUNCTION PF_Test(int)
> >> AS RANGE FOR VALUES();
> >>
> >>
> >> --
> >> Hope this s.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >> http://weblogs.sqlteam.com/dang/
> >>
> >> "Nam" <Nam@discussions.microsoft.com> wrote in message
> >> news:E5F176A2-5879-4203-81DF-A7A23BA6D5AB@microsoft.com...
> >> >I first tried to upgrade the default instance of our SQL Server 2005 SP2
> >> >from
> >> > the Standard Edition to Enterprise Edition from the CD and I got the
> >> > following message:
> >> >
> >> > “Edition Change Check (Warning): To change an existing instance of
> >> > Microsoft
> >> > SQL Server 2005 to a different edition of SQL Server 2005, you must run
> >> > SQL
> >> > Server 2005 Setup from the command prompt and include the SKUUPGRADE=1
> >> > parameter�
> >> >
> >> > Then I run the following command from DOS prompt [Ref:
> >> > http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
> >> >
> >> > start /wait setup.exe ADDLOCAL=SQL_Engine INSTANCENAME=MSSQLSERVER
> >> > UPGRADE=SQL_Engine SKUUPGRADE=1 /qb
> >> >
> >> > The above command ran only for less than TWO minutes. I was a little
> >> > suspicious that the upgrade would be completed within two minutes. So,
> >> > I
> >> > ran
> >> > the following query on the query analyzer:
> >> >
> >> > SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY
> >> > ('productlevel'),
> >> > SERVERPROPERTY ('edition')
> >> >
> >> > And the result of the above query was as follows:
> >> >
> >> > 9.00.3042.00 SP2 Enterprise Edition
> >> >
> >> > But according to MSDN [Ref:
> >> > http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
> >> >
> >> > “If you use the SKUUPGRADE parameter, Setup will remove all hotfix and
> >> > service pack updates from the SQL Server instance being upgraded. Once
> >> > the
> >> > edition upgrade is complete, you must reapply all hotfix and service
> >> > pack
> >> > updates.�
> >> >
> >> > My Question is: How come upgrade was completed within two minutes and
> >> > that
> >> > it did not remove SP2. Is there any way I can verify from any feature
> >> > that
> >> > Enterprise edition has but Standard edition does not? Or any other way
> >> > of
> >> > verifying that indeed we have enterprise edition running? We have only
> >> > Database Engine and SQL Server Reporting Services installed.
> >> >
> >> > Thank You.
> >>
>

> Is there anything specific I should look into the above files. Following
> is
> all the content from the last of the above files:

The summary.txt file in the parent LOG folder should indicate which
component(s) failed. Check the corresponding log in the Files folder as
indicated in http://msdn.microsoft.com/en-us/library/ms143702.aspx for
related errors. The setup messages can be rather encryptic but will
hopefully indicate the root cause.

--
Hope this s.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"Nam" <Nam@discussions.microsoft.com> wrote in message
news:BC3AFF54-57A2-462A-A9F4-07F15E28852A@microsoft.com...
> Dan,
>
> Thank you for trying to . I found the following four files in
> C:\Program
> Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files that were created
> at
> the time of upgrade process:
>
> SQLSetup0003_MYMACHINENAME_Support.log
> SQLSetup0003_MYMACHINENAME_SCC.log
> SQLSetup0003_MYMACHINENAME_Core(Patched).log
> SQLSetup0003_MYMACHINENAME_Core.log
>
> Is there anything specific I should look into the above files. Following
> is
> all the content from the last of the above files:
>
> Microsoft SQL Server 2005 Setup beginning at Thu May 01 18:31:19 2008
> Process ID : 5460
> F:\setup.exe Version: 2005.90.1399.0
> Running: LoadResourcesAction at: 2008/4/1 18:31:15
> Complete: LoadResourcesAction at: 2008/4/1 18:31:15, returned true
> Running: ParseBootstrapOptionsAction at: 2008/4/1 18:31:15
> Loaded DLL:F:\xmlrw.dll Version:2.0.3604.0
> Complete: ParseBootstrapOptionsAction at: 2008/4/1 18:31:18, returned true
> Running: ValidateWinNTAction at: 2008/4/1 18:31:18
> Complete: ValidateWinNTAction at: 2008/4/1 18:31:18, returned true
> Running: ValidateMinOSAction at: 2008/4/1 18:31:18
> Complete: ValidateMinOSAction at: 2008/4/1 18:31:18, returned true
> Running: PerformSCCAction at: 2008/4/1 18:31:18
> Complete: PerformSCCAction at: 2008/4/1 18:31:19, returned true
> Running: ActivateLoggingAction at: 2008/4/1 18:31:19
> Complete: ActivateLoggingAction at: 2008/4/1 18:31:20, returned true
> Running: DetectPatchedBootstrapAction at: 2008/4/1 18:31:20
> Complete: DetectPatchedBootstrapAction at: 2008/4/1 18:31:21, returned
> true
> Running: LaunchPatchedBootstrapAction at: 2008/4/1 18:31:24
> Error: Action "LaunchPatchedBootstrapAction" threw an exception during
> execution. Error information reported during run:
> "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe"
> finished and returned: 0
> Aborting queue processing as nested installer has completed
> Message pump returning: 0
>
> Thank you.......
>
>
> "Dan Guzman" wrote:
>
>> Hi, Nam.
>>
>> It's been a long while since I did an SKUUPRGRADE so I tested one one
>> against a SE SP2 test vpc machine. After the she successful upgrade,
>>
>> SELECT
>> SERVERPROPERTY('productversion'),
>> SERVERPROPERTY ('productlevel'),
>> SERVERPROPERTY ('edition')
>>
>> Returns:
>>
>> 9.00.1399.06 RTM Enterprise Edition
>>
>> and a CREATE PARTITION FUNCTION succeeded. After the SP2 install, the
>> query
>> returned:
>>
>> 9.00.3042.00 SP2 Enterprise Edition
>>
>> Have you checked the setup log files (in C:\Program Files\Microsoft SQL
>> Server\90\Setup Bootstrap\LOG\Files) for errors?
>>
>> --
>> Hope this s.
>>
>> Dan Guzman
>> SQL Server MVP
>> http://weblogs.sqlteam.com/dang/
>>
>> "Nam" <Nam@discussions.microsoft.com> wrote in message
>> news:9AA270EB-7452-46BF-814A-8BCF07B6AF5C@microsoft.com...
>> > Thank you so much for your . I ran your SQL query on our Standard
>> > Edition
>> > and got the following message:
>> >
>> > “Msg 7736, Level 16, State 1, Line 2
>> > Partition function can only be created in Enterprise edition of SQL
>> > Server.
>> > Only Enterprise edition of SQL Server supports partitioning.�
>> >
>> > Whereas, the query ran successfully on the server in question (that I
>> > upgraded to Enterprise Edition).
>> >
>> > The mystery remains as to how the command line prompt upgraded the
>> > Server
>> > to
>> > EE within less than two minutes and why SP2 was not removed whereas the
>> > MSDN
>> > article clearly states the following: “If you use the SKUUPGRADE
>> > parameter,
>> > Setup will REMOVE all hotfix and service pack updates from the SQL
>> > Server
>> > instance being upgraded�
>> >
>> > Was there anything got missed in my upgrade process and is there
>> > anything
>> > else I need to do in order to make sure we are working on a 100%
>> > Enterprise
>> > Edition and to avoid any problems in future when all the applications
>> > connected to SQL Server are already installed and running?
>> >
>> > We have only two machines (Win 2003) both had only one instance of SQL
>> > 2005
>> > Standard Edition one of which we upgraded to Enterprise Edition. Both
>> > instances are default instances.
>> >
>> > Thank you.....
>> >
>> > "Dan Guzman" wrote:
>> >
>> >> > “If you use the SKUUPGRADE parameter, Setup will remove all hotfix
>> >> > and
>> >> > service pack updates from the SQL Server instance being upgraded.
>> >> > Once
>> >> > the
>> >> > edition upgrade is complete, you must reapply all hotfix and service
>> >> > pack
>> >> > updates.�
>> >> >
>> >> > My Question is: How come upgrade was completed within two minutes
>> >> > and
>> >> > that
>> >> > it did not remove SP2.
>> >>
>> >> Note that the article does not say that SP2 is removed by the upgrade.
>> >> It
>> >> states that it needs to be reapplied after the upgrade.
>> >>
>> >> > Is there any way I can verify from any feature that
>> >> > Enterprise edition has but Standard edition does not? Or any other
>> >> > way
>> >> > of
>> >> > verifying that indeed we have enterprise edition running? We have
>> >> > only
>> >> > Database Engine and SQL Server Reporting Services installed.
>> >>
>> >> Partitioning is a feature available in EE and DE only so I would
>> >> expect
>> >> the
>> >> following statement to fail. I don't have a standard instance to test
>> >> this
>> >> on, though.
>> >>
>> >> CREATE PARTITION FUNCTION PF_Test(int)
>> >> AS RANGE FOR VALUES();
>> >>
>> >>
>> >> --
>> >> Hope this s.
>> >>
>> >> Dan Guzman
>> >> SQL Server MVP
>> >> http://weblogs.sqlteam.com/dang/
>> >>
>> >> "Nam" <Nam@discussions.microsoft.com> wrote in message
>> >> news:E5F176A2-5879-4203-81DF-A7A23BA6D5AB@microsoft.com...
>> >> >I first tried to upgrade the default instance of our SQL Server 2005
>> >> >SP2
>> >> >from
>> >> > the Standard Edition to Enterprise Edition from the CD and I got the
>> >> > following message:
>> >> >
>> >> > “Edition Change Check (Warning): To change an existing instance of
>> >> > Microsoft
>> >> > SQL Server 2005 to a different edition of SQL Server 2005, you must
>> >> > run
>> >> > SQL
>> >> > Server 2005 Setup from the command prompt and include the
>> >> > SKUUPGRADE=1
>> >> > parameter�
>> >> >
>> >> > Then I run the following command from DOS prompt [Ref:
>> >> > http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
>> >> >
>> >> > start /wait setup.exe ADDLOCAL=SQL_Engine INSTANCENAME=MSSQLSERVER
>> >> > UPGRADE=SQL_Engine SKUUPGRADE=1 /qb
>> >> >
>> >> > The above command ran only for less than TWO minutes. I was a little
>> >> > suspicious that the upgrade would be completed within two minutes.
>> >> > So,
>> >> > I
>> >> > ran
>> >> > the following query on the query analyzer:
>> >> >
>> >> > SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY
>> >> > ('productlevel'),
>> >> > SERVERPROPERTY ('edition')
>> >> >
>> >> > And the result of the above query was as follows:
>> >> >
>> >> > 9.00.3042.00 SP2 Enterprise Edition
>> >> >
>> >> > But according to MSDN [Ref:
>> >> > http://msdn.microsoft.com/en-us/library/ms144259.aspx]:
>> >> >
>> >> > “If you use the SKUUPGRADE parameter, Setup will remove all hotfix
>> >> > and
>> >> > service pack updates from the SQL Server instance being upgraded.
>> >> > Once
>> >> > the
>> >> > edition upgrade is complete, you must reapply all hotfix and service
>> >> > pack
>> >> > updates.�
>> >> >
>> >> > My Question is: How come upgrade was completed within two minutes
>> >> > and
>> >> > that
>> >> > it did not remove SP2. Is there any way I can verify from any
>> >> > feature
>> >> > that
>> >> > Enterprise edition has but Standard edition does not? Or any other
>> >> > way
>> >> > of
>> >> > verifying that indeed we have enterprise edition running? We have
>> >> > only
>> >> > Database Engine and SQL Server Reporting Services installed.
>> >> >
>> >> > Thank You.
>> >>
>>