RE: Upgrading to SQL 2005 ENT
- From: Lucas Kartawidjaja <LucasKartawidjaja@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 7 Oct 2009 11:48:01 -0700
I am wondering, when you get into components to install, do you choose
Reporting services as well? For reporting services, you will generally need
IIS installed. Try not including the Reporting Services. I am a bit concern
about the server not fulfilling the hardware requirement. What's the free
disk space, RAM and CPU that you've assigned to the virtual system?
By the way, you might want to look at this article:
http://articles.techrepublic.com.com/5100-10878_11-6036309.html
It gives a good step by step how to on upgrading to SQL Server 2005.
Thank you
Lucas
"tnt" wrote:
I finally rerun it. This time I choose the default instance and then checked.
the box that reads "SQL Server Database Services 8.00.2039 (before I didn't
check this) at the Existing components.
Not I am getting this error "AdvisorUpgrade returned -1" during the Analyze
upgrade part.
Tnt
"tnt" wrote:
Forgot to add that I did choose the "Default Instance".
Tnt
"tnt" wrote:
Lucas,
I drilled down to the setup directory and ran setup.exe. There wasn't a
link to that tell me to upgrade.
Since looking at the log, I might not have IIS installed which might have
caused my problem? i am running this on a virtual environment.
Tnt
Below is the log:
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise Edition
Service Pack 2 (Build 3790)
Time : Mon Oct 05 17:13:57 2009
mysql1 : The current system does not meet minimum hardware requirements for
this SQL Server release. For detailed hardware requirements, see the readme
file or SQL Server Books Online.
mysql1 : Microsoft Internet Information Services (IIS) is either not
installed or is disabled. IIS is required by some SQL Server features.
Without IIS, some SQL Server features will not be available for installation.
To install all SQL Server features, install IIS from Add or Remove Programs
in Control Panel or enable the IIS service through the Control Panel if it is
already installed, and then run SQL Server Setup again. For a list of
features that depend on IIS, see Features Supported by Editions of SQL Server
in Books Online.
Machine : mysql1
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_mysql1_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : mysql1
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_mysql1_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : mysql1
Product : Microsoft Visual Studio 2005 Premier Partner Edition - ENU
Product Version : 8.0.50727.42
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_mysql1_PPESku_1.log
--------------------------------------------------------------------------------
Machine : mysql1
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_mysql1_OWC11_1.log
--------------------------------------------------------------------------------
Machine : mysql1
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_mysql1_BOL_1.log
--------------------------------------------------------------------------------
Machine : mysql1
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_mysql1_BackwardsCompat_1.log
--------------------------------------------------------------------------------
Machine : mysql1
Product : MSXML 6.0 Parser (KB933579)
Product Version : 6.10.1200.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_mysql1_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : mysql1
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_mysql1_SQLXML4_1.log
--------------------------------------------------------------------------------
Machine : mysql1
Product : Microsoft SQL Server 2005 Tools
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_mysql1_Tools.log
--------------------------------------------------------------------------------
Setup succeeded with the installation, inspect the log file completely for
status on all the components.
Time : Mon Oct 05 17:29:44 2009
"Lucas Kartawidjaja" wrote:
When you run SELECT @@Version, it should give you the version of the database
engine, not the sql server management studio or enterprise manager. You
mentioned that you got 8.00.2039 as the version. That would mean that your
database engine is still SQL Server 2000.
I am just wondering, when you do the installation, what option do you
choose? Also what operating system do you have on your server? It seems like
when you are doing the installation, you are installing just the SQL client
tool (such as the SQL Server Management Studio) and not upgrading the
database engine to SQL Server 2005. You might want to check the installation
setup file, usually located under C:\Program Files\ Microsoft SQL
Server\90\Setup Bootstrap\LOG\.
Thank you
Lucas
"tnt" wrote:
The sql server management studio version is 8.00.2039 with SELECT @@Version
command.
It has the same version from the Enterprise Manager. Now I am confused.
Tnt
"Lucas Kartawidjaja" wrote:
Out of the top of my head, I could not remember if the in-place upgrade
remove the SQL Enterprise Manager or not. On Studio Manager, try running
SELECT @@Version, that should give the version of the SQL Server that you
have.
Enterprise Manager and Studio Manager are just client/management tool.
Enterprise Manager can be use to connect to SQL Server 2005, and also Studio
Manager can also be use to connect to SQL Server 2000.
Thank you
Lucas
"tnt" wrote:
Hello,
I just run a test upgrade on SQL 2000 ENT (SP4) to SQL 2005 ENT. I took the
default instance (in place upgrade?).
The installation completes successfully. I noticed there still exists the
SQL Enterprise manager from the SQL 2000 version. The databases are visible
on the Enterprise Manager 2000 and the new SQL Server Management Studio.
I did a test by bringing a database offline/online and it seems the action
taken on the Enterprise manager (2000) or Studio Manager (2005) will reflect
the change by the other.
Is this how it supposed to be? I did download the technical reference but
thought I run through this site first.
TIA,
tnt
- Follow-Ups:
- RE: Upgrading to SQL 2005 ENT
- From: tnt
- RE: Upgrading to SQL 2005 ENT
- References:
- Upgrading to SQL 2005 ENT
- From: tnt
- RE: Upgrading to SQL 2005 ENT
- From: Lucas Kartawidjaja
- RE: Upgrading to SQL 2005 ENT
- From: tnt
- RE: Upgrading to SQL 2005 ENT
- From: Lucas Kartawidjaja
- RE: Upgrading to SQL 2005 ENT
- From: tnt
- RE: Upgrading to SQL 2005 ENT
- From: tnt
- RE: Upgrading to SQL 2005 ENT
- From: tnt
- Upgrading to SQL 2005 ENT
- Prev by Date: Re: Why does a restore create the app_log.ldf file as app_1.ldf?
- Next by Date: Re: Changing Server Name and Domain
- Previous by thread: RE: Upgrading to SQL 2005 ENT
- Next by thread: RE: Upgrading to SQL 2005 ENT
- Index(es):
Relevant Pages
|
Loading
