IA64 teradata OLE-DB or ODBC

I have a 32 bit development/playbox SQL 2005 SSIS that can see and run 32 bit OLE DB drivers from Teradata. Granted I have the same issues as others where a table or a view would work and not a query or a variable query. The alternative is to use Linked Server and OPENQUERY.

But our real development box is a 64 bit IA 64 using 64 bit SQL 2005. Non of the Teradata.com drivers would work/show up in the dropdown box of the Connection Manager since they are 32 bit. One option is to use the 64 bit Teradata ODBC drivers and then use the .Net ODBC connection instead. Linked server doesn't work either because the SQL 2005 is 64 bit and it is looking for 64 bit drivers.

Has anyone have any experience with 64 bit SQL 2005 and Teradata?

Looked at other 3rd party vendors such as ETI but their documentation excludes IA 64 (Itanium).

Planning to try again using the 64 bit ODBC and .Net Adapter but I'm interested to hear if someone (MSFT & NCR) would have a real solution for 64 bit.

Thanks

Anatole

I'm replying to my own thread as I want to see who else is having the same issue using Teradata Drivers and SSIS (32 or 64 bit).

I think this is a given where the Teradata OLE-DB driver is failing when used as a SQL Stmt rather than Table/View to extract data.

The message is:

An OLE DB error has occurred. Error code: 0x80040E21.An OLE DB record is available. Source: "OLE DB Provider for Teradata" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done."

Has anyone found a work-around and/or contacted MS about this?

I opened a ticket with teradata/ncr but they are pointing back at SSIS and MS.

This error can occur on any box/cpu (32 bit or 64bit).

Since ODBC adaptor in SSIS converts everything into UNICODE, the only option is to use Linkedserver and OPENQUERY cmd.

I would like to hear back from MS (I know thay have teradata servers) or anyone that has either received this error and has a solution OR is also waiting on one.

Thanks

Anatole

|||

Anatole,

Take a look at :

www.openlinksw.com/

They seem to have an IA64 OLE to ODBC driver. I am not sure I even understand the issue well enough, but we had a similar issue and found them, we are still looking to see if they can solve our issue witch is with Sybase and SQL, but I thought I would just throw it out there for you since you had not gotten anyone to reply back, it might at least give you a better lead....

Hope it helps...

Steve

|||

2 other potential resources are:

www.odbcsdk.com

This is another Third Party (Open Access) that advertises a 64bit OLEDB to ODBC Data Provider (Itanium).

http://www.datadirect.com/products/odbc64/overview/index.ssp

This is another Third Party (DataDirect) that advertises a 64bit Sybase ODBC driver (Itanium)

Just trying to be helpful for people running into these types of problems....Hopefully this is helpful...

Steve

|||

Hi!

See also my similar question (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=853174&SiteID=1&mode=1).

I can't work out your suggestion using a ".net ODBC".

B.G.

IA64 teradata OLE-DB or ODBC

I have a 32 bit development/playbox SQL 2005 SSIS that can see and run 32 bit OLE DB drivers from Teradata. Granted I have the same issues as others where a table or a view would work and not a query or a variable query. The alternative is to use Linked Server and OPENQUERY.

But our real development box is a 64 bit IA 64 using 64 bit SQL 2005. Non of the Teradata.com drivers would work/show up in the dropdown box of the Connection Manager since they are 32 bit. One option is to use the 64 bit Teradata ODBC drivers and then use the .Net ODBC connection instead. Linked server doesn't work either because the SQL 2005 is 64 bit and it is looking for 64 bit drivers.

Has anyone have any experience with 64 bit SQL 2005 and Teradata?

Looked at other 3rd party vendors such as ETI but their documentation excludes IA 64 (Itanium).

Planning to try again using the 64 bit ODBC and .Net Adapter but I'm interested to hear if someone (MSFT & NCR) would have a real solution for 64 bit.

Thanks

Anatole

I'm replying to my own thread as I want to see who else is having the same issue using Teradata Drivers and SSIS (32 or 64 bit).

I think this is a given where the Teradata OLE-DB driver is failing when used as a SQL Stmt rather than Table/View to extract data.

The message is:

An OLE DB error has occurred. Error code: 0x80040E21.An OLE DB record is available. Source: "OLE DB Provider for Teradata" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done."

Has anyone found a work-around and/or contacted MS about this?

I opened a ticket with teradata/ncr but they are pointing back at SSIS and MS.

This error can occur on any box/cpu (32 bit or 64bit).

Since ODBC adaptor in SSIS converts everything into UNICODE, the only option is to use Linkedserver and OPENQUERY cmd.

I would like to hear back from MS (I know thay have teradata servers) or anyone that has either received this error and has a solution OR is also waiting on one.

Thanks

Anatole

|||

Anatole,

Take a look at :

www.openlinksw.com/

They seem to have an IA64 OLE to ODBC driver. I am not sure I even understand the issue well enough, but we had a similar issue and found them, we are still looking to see if they can solve our issue witch is with Sybase and SQL, but I thought I would just throw it out there for you since you had not gotten anyone to reply back, it might at least give you a better lead....

Hope it helps...

Steve

|||

2 other potential resources are:

www.odbcsdk.com

This is another Third Party (Open Access) that advertises a 64bit OLEDB to ODBC Data Provider (Itanium).

http://www.datadirect.com/products/odbc64/overview/index.ssp

This is another Third Party (DataDirect) that advertises a 64bit Sybase ODBC driver (Itanium)

Just trying to be helpful for people running into these types of problems....Hopefully this is helpful...

Steve

|||

Hi!

See also my similar question (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=853174&SiteID=1&mode=1).

I can't work out your suggestion using a ".net ODBC".

B.G.

sql

IA64 SP4 Install Problem

I am having trouble installing SP4 on my IA64. Like the instructions said in
section 1.1 of the help file I have changed it to allow Unsigned drivers to
Silently Succeed. However I am still getting a failure.
On thing to note when I run the following command I get some different
results than the help file say I sould.
SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
SERVERPROPERTY('ProductVersion')
SP3
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit) on
Windows NT 5.2 (Build 3790: )
8.00.818
About a year ago MS and Oracle were working with me to solve a memory leak
issue and I think that may be related to why SP4 wont install but I cant be
sure.
The only hint as to what the error is at the begining of the logfile (See
below).
05/18/2005 08:29:49.910
================================================== ==============================
05/18/2005 08:29:49.910 Hotfix package launched
05/18/2005 08:29:49.910 Local Computer:
05/18/2005 08:29:49.910 Target Details: SG1
05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:49.910 windir = C:\WINDOWS
05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
05/18/2005 08:29:49.910
05/18/2005 08:29:50.850 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 Product Details:
05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
05/18/2005 08:29:51.110 build = 2039
05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
05/18/2005 08:29:51.110 details = This Service Pack can be applied on all
SQL Server 2000 64-bit features including the relational database engine and
Analysis Services. If you have not done so already, back up the master and
msdb databases and stop all database programs and services before proceeding.
05/18/2005 08:29:51.110 kbarticle = KB884525
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 package = HotFix1
05/18/2005 08:29:51.110 productname = SQLOLAP64
05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Service
Pack 4
05/18/2005 08:29:51.110 splevel = RTM,4
05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:51.110 version = 8
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 File Group Details: MSP
05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress
05/18/2005 08:29:51.110 File Details: sqlrun.msp
05/18/2005 08:29:51.110 lockedfilecheck = 1
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 Instance Details: MSSQLServer
05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
05/18/2005 08:29:51.110 default = TRUE
05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
05/18/2005 08:29:51.110 id = MSSQLServer
05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
SQL Server\MSSQL
05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
Server\MSSQL
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 name = MSSQLServer
05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
05/18/2005 08:29:51.110 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.110 servicename = MSSQLServer
05/18/2005 08:29:51.110 sku = ENTERPRISE
05/18/2005 08:29:51.110 sp = RTM
05/18/2005 08:29:51.110 type = Liberty
05/18/2005 08:29:51.110 version = 8
Anybody?
"Jim" wrote:

> I am having trouble installing SP4 on my IA64. Like the instructions said in
> section 1.1 of the help file I have changed it to allow Unsigned drivers to
> Silently Succeed. However I am still getting a failure.
> On thing to note when I run the following command I get some different
> results than the help file say I sould.
> SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
> SERVERPROPERTY('ProductVersion')
> SP3
> Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit) on
> Windows NT 5.2 (Build 3790: )
> 8.00.818
> About a year ago MS and Oracle were working with me to solve a memory leak
> issue and I think that may be related to why SP4 wont install but I cant be
> sure.
> The only hint as to what the error is at the begining of the logfile (See
> below).
> 05/18/2005 08:29:49.910
> ================================================== ==============================
> 05/18/2005 08:29:49.910 Hotfix package launched
> 05/18/2005 08:29:49.910 Local Computer:
> 05/18/2005 08:29:49.910 Target Details: SG1
> 05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
> 05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
> 05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:49.910 windir = C:\WINDOWS
> 05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
> 05/18/2005 08:29:49.910
> 05/18/2005 08:29:50.850 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 Product Details:
> 05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
> 05/18/2005 08:29:51.110 build = 2039
> 05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
> 05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
> 05/18/2005 08:29:51.110 details = This Service Pack can be applied on all
> SQL Server 2000 64-bit features including the relational database engine and
> Analysis Services. If you have not done so already, back up the master and
> msdb databases and stop all database programs and services before proceeding.
> 05/18/2005 08:29:51.110 kbarticle = KB884525
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 package = HotFix1
> 05/18/2005 08:29:51.110 productname = SQLOLAP64
> 05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Service
> Pack 4
> 05/18/2005 08:29:51.110 splevel = RTM,4
> 05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:51.110 version = 8
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 File Group Details: MSP
> 05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
> 05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress
> 05/18/2005 08:29:51.110 File Details: sqlrun.msp
> 05/18/2005 08:29:51.110 lockedfilecheck = 1
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
> SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 Instance Details: MSSQLServer
> 05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
> 05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
> 05/18/2005 08:29:51.110 default = TRUE
> 05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
> 05/18/2005 08:29:51.110 id = MSSQLServer
> 05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
> SQL Server\MSSQL
> 05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
> Server\MSSQL
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 name = MSSQLServer
> 05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
> 05/18/2005 08:29:51.110 productcode =
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.110 servicename = MSSQLServer
> 05/18/2005 08:29:51.110 sku = ENTERPRISE
> 05/18/2005 08:29:51.110 sp = RTM
> 05/18/2005 08:29:51.110 type = Liberty
> 05/18/2005 08:29:51.110 version = 8
|||Sorry don't have an answer for you. If no one else pipes in you may want to
give MS PSS a call.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:D129328E-93E4-4E2A-BC6B-129B9D7341AE@.microsoft.com...[vbcol=seagreen]
> Anybody?
> "Jim" wrote:
|||I'm getting the same error as well. I'm thinking it has something to
do with a previous version of a hotfix that was applied:
SELECT @.@.Version
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003
15:32:45 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
Edition (64-bit) on Windows NT 5.2 (Build 3790: )
05/26/2005 21:10:33.107
================================================== ==============================
05/26/2005 21:10:33.107 Hotfix package launched
05/26/2005 21:10:33.107 Local Computer:
05/26/2005 21:10:33.107 Target Details: OLYMPOS
05/26/2005 21:10:33.107 commonfilesdir = C:\Program Files\Common
Files
05/26/2005 21:10:33.107 programfilesdir = C:\Program Files
05/26/2005 21:10:33.107 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:33.107 windir = C:\WINDOWS
05/26/2005 21:10:33.107 winsysdir = C:\WINDOWS\system32
05/26/2005 21:10:33.107
05/26/2005 21:10:34.756 The following product instance was
disqualified because a parent product instance of the same product
code was found: {0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.959 The following product instance was
disqualified because a parent product instance of the same product
code was found: {FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.959 Product Details:
05/26/2005 21:10:34.959 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.959 build = 2039
05/26/2005 21:10:34.959 description = SQL Server 2000 (64-bit)
05/26/2005 21:10:34.959 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.959 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.959 kbarticle = KB884525
05/26/2005 21:10:34.959 lcid = 1033
05/26/2005 21:10:34.959 package = HotFix1
05/26/2005 21:10:34.959 productname = SQLOLAP64
05/26/2005 21:10:34.959 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.959 splevel = RTM,4
05/26/2005 21:10:34.959 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.959 version = 8
05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 File Group Details: MSP
05/26/2005 21:10:34.959 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.959 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.959 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.959 File Details: sqlrun.msp
05/26/2005 21:10:34.959 lockedfilecheck = 1
05/26/2005 21:10:34.959 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 Instance Details: PRODUCTION
05/26/2005 21:10:34.959 = Software\Microsoft\Microsoft SQL
Server\PRODUCTION\Setup
05/26/2005 21:10:34.959 agentservicename = SQLAgent$PRODUCTION
05/26/2005 21:10:34.959 hiveregpath = Software\Microsoft\Microsoft
SQL Server\PRODUCTION
05/26/2005 21:10:34.959 id = PRODUCTION
05/26/2005 21:10:34.959 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$PRODUCTION
05/26/2005 21:10:34.959 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$PRODUCTION
05/26/2005 21:10:34.959 lcid = 1033
05/26/2005 21:10:34.969 name = PRODUCTION
05/26/2005 21:10:34.969 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.969 servicename = MSSQL$PRODUCTION
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = Liberty
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWORK
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQL
Server\RMSWORK\Setup
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWORK
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = Liberty
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWORK
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWORK
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = OLAP
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = SQL Server 2000 (64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: SQL Tools
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\80\Tools
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = SQL Tools
05/26/2005 21:10:34.969 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: OLAPClient
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Common
Files\system\OLE DB
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = OLAPClient
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:51.286 Authenticating user using Windows
Authentication
05/26/2005 21:10:51.306 SQL Service MSSQL$PRODUCTION was previously
running, ready for authentication
05/26/2005 21:10:51.306 SQL Agent Service SQLAgent$PRODUCTION was
previously running
05/26/2005 21:10:51.489 User authentication was successful
05/26/2005 21:10:54.787 Attempting to install product: SQLOLAP64
|||Hi there:
i am also facing the same problem when i try installing SQL2k SP4 on IA serversWere you able ti fix it. Will appreciate any help.
Kind Regards,
Roshan
From http://www.developmentnow.com/g/118_2005_5_0_0_524275/IA64-SP4-Install-Problem.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com

IA64 SP4 Install Problem

I am having trouble installing SP4 on my IA64. Like the instructions said in
section 1.1 of the help file I have changed it to allow Unsigned drivers to
Silently Succeed. However I am still getting a failure.
On thing to note when I run the following command I get some different
results than the help file say I sould.
SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
SERVERPROPERTY('ProductVersion')
SP3
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit) o
n
Windows NT 5.2 (Build 3790: )
8.00.818
About a year ago MS and Oracle were working with me to solve a memory leak
issue and I think that may be related to why SP4 wont install but I cant be
sure.
The only hint as to what the error is at the begining of the logfile (See
below).
05/18/2005 08:29:49.910
========================================
====================================
====
05/18/2005 08:29:49.910 Hotfix package launched
05/18/2005 08:29:49.910 Local Computer:
05/18/2005 08:29:49.910 Target Details: SG1
05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:49.910 windir = C:\WINDOWS
05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
05/18/2005 08:29:49.910
05/18/2005 08:29:50.850 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 Product Details:
05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
05/18/2005 08:29:51.110 build = 2039
05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
05/18/2005 08:29:51.110 details = This Service Pack can be applied on all
SQL Server 2000 64-bit features including the relational database engine and
Analysis Services. If you have not done so already, back up the master and
msdb databases and stop all database programs and services before proceeding
.
05/18/2005 08:29:51.110 kbarticle = KB884525
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 package = HotFix1
05/18/2005 08:29:51.110 productname = SQLOLAP64
05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Service
Pack 4
05/18/2005 08:29:51.110 splevel = RTM,4
05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:51.110 version = 8
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 File Group Details: MSP
05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress
05/18/2005 08:29:51.110 File Details: sqlrun.msp
05/18/2005 08:29:51.110 lockedfilecheck = 1
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 Instance Details: MSSQLServer
05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
05/18/2005 08:29:51.110 default = TRUE
05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
05/18/2005 08:29:51.110 id = MSSQLServer
05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
SQL Server\MSSQL
05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
Server\MSSQL
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 name = MSSQLServer
05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
05/18/2005 08:29:51.110 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.110 servicename = MSSQLServer
05/18/2005 08:29:51.110 sku = ENTERPRISE
05/18/2005 08:29:51.110 sp = RTM
05/18/2005 08:29:51.110 type = Liberty
05/18/2005 08:29:51.110 version = 8Anybody?
"Jim" wrote:

> I am having trouble installing SP4 on my IA64. Like the instructions said
in
> section 1.1 of the help file I have changed it to allow Unsigned drivers t
o
> Silently Succeed. However I am still getting a failure.
> On thing to note when I run the following command I get some different
> results than the help file say I sould.
> SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
> SERVERPROPERTY('ProductVersion')
> SP3
> Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit)
on
> Windows NT 5.2 (Build 3790: )
> 8.00.818
> About a year ago MS and Oracle were working with me to solve a memory leak
> issue and I think that may be related to why SP4 wont install but I cant b
e
> sure.
> The only hint as to what the error is at the begining of the logfile (See
> below).
> 05/18/2005 08:29:49.910
> ========================================
==================================
======
> 05/18/2005 08:29:49.910 Hotfix package launched
> 05/18/2005 08:29:49.910 Local Computer:
> 05/18/2005 08:29:49.910 Target Details: SG1
> 05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
> 05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
> 05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:49.910 windir = C:\WINDOWS
> 05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
> 05/18/2005 08:29:49.910
> 05/18/2005 08:29:50.850 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 Product Details:
> 05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
> 05/18/2005 08:29:51.110 build = 2039
> 05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
> 05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
> 05/18/2005 08:29:51.110 details = This Service Pack can be applied on al
l
> SQL Server 2000 64-bit features including the relational database engine a
nd
> Analysis Services. If you have not done so already, back up the master an
d
> msdb databases and stop all database programs and services before proceedi
ng.
> 05/18/2005 08:29:51.110 kbarticle = KB884525
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 package = HotFix1
> 05/18/2005 08:29:51.110 productname = SQLOLAP64
> 05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Servi
ce
> Pack 4
> 05/18/2005 08:29:51.110 splevel = RTM,4
> 05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:51.110 version = 8
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 File Group Details: MSP
> 05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
> 05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress
> 05/18/2005 08:29:51.110 File Details: sqlrun.msp
> 05/18/2005 08:29:51.110 lockedfilecheck = 1
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
> SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 Instance Details: MSSQLServer
> 05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
> 05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
> 05/18/2005 08:29:51.110 default = TRUE
> 05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
> 05/18/2005 08:29:51.110 id = MSSQLServer
> 05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
> SQL Server\MSSQL
> 05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
> Server\MSSQL
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 name = MSSQLServer
> 05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
> 05/18/2005 08:29:51.110 productcode =
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.110 servicename = MSSQLServer
> 05/18/2005 08:29:51.110 sku = ENTERPRISE
> 05/18/2005 08:29:51.110 sp = RTM
> 05/18/2005 08:29:51.110 type = Liberty
> 05/18/2005 08:29:51.110 version = 8|||Sorry don't have an answer for you. If no one else pipes in you may want to
give MS PSS a call.
http://support.microsoft.com/defaul...id=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:D129328E-93E4-4E2A-BC6B-129B9D7341AE@.microsoft.com...[vbcol=seagreen]
> Anybody?
> "Jim" wrote:
>|||I'm getting the same error as well. I'm thinking it has something to
do with a previous version of a hotfix that was applied:
SELECT @.@.Version
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003
15:32:45 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
Edition (64-bit) on Windows NT 5.2 (Build 3790: )
05/26/2005 21:10:33.107
========================================
====================================
====
05/26/2005 21:10:33.107 Hotfix package launched
05/26/2005 21:10:33.107 Local Computer:
05/26/2005 21:10:33.107 Target Details: OLYMPOS
05/26/2005 21:10:33.107 commonfilesdir = C:\Program Files\Common
Files
05/26/2005 21:10:33.107 programfilesdir = C:\Program Files
05/26/2005 21:10:33.107 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:33.107 windir = C:\WINDOWS
05/26/2005 21:10:33.107 winsysdir = C:\WINDOWS\system32
05/26/2005 21:10:33.107
05/26/2005 21:10:34.756 The following product instance was
disqualified because a parent product instance of the same product
code was found: {0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.959 The following product instance was
disqualified because a parent product instance of the same product
code was found: {FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.959 Product Details:
05/26/2005 21:10:34.959 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotF
ix1.inf
05/26/2005 21:10:34.959 build = 2039
05/26/2005 21:10:34.959 description = SQL Server 2000 (64-bit)
05/26/2005 21:10:34.959 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.959 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.959 kbarticle = KB884525
05/26/2005 21:10:34.959 lcid = 1033
05/26/2005 21:10:34.959 package = HotFix1
05/26/2005 21:10:34.959 productname = SQLOLAP64
05/26/2005 21:10:34.959 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.959 splevel = RTM,4
05/26/2005 21:10:34.959 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.959 version = 8
05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 File Group Details: MSP
05/26/2005 21:10:34.959 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.959 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.959 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.959 File Details: sqlrun.msp
05/26/2005 21:10:34.959 lockedfilecheck = 1
05/26/2005 21:10:34.959 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 Instance Details: PRODUCTION
05/26/2005 21:10:34.959 = Software\Microsoft\Microsoft SQL
Server\PRODUCTION\Setup
05/26/2005 21:10:34.959 agentservicename = SQLAgent$PRODUCTION
05/26/2005 21:10:34.959 hiveregpath = Software\Microsoft\Microsoft
SQL Server\PRODUCTION
05/26/2005 21:10:34.959 id = PRODUCTION
05/26/2005 21:10:34.959 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$PRODUCTION
05/26/2005 21:10:34.959 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$PRODUCTION
05/26/2005 21:10:34.959 lcid = 1033
05/26/2005 21:10:34.969 name = PRODUCTION
05/26/2005 21:10:34.969 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.969 servicename = MSSQL$PRODUCTION
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = Liberty
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWORK
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQL
Server\RMSWORK\Setup
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWORK
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = Liberty
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotF
ix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWORK
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWORK
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = OLAP
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotF
ix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = SQL Server 2000 (64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: SQL Tools
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\80\Tools
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = SQL Tools
05/26/2005 21:10:34.969 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotF
ix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: OLAPClient
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Common
Files\system\OLE DB
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = OLAPClient
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:51.286 Authenticating user using Windows
Authentication
05/26/2005 21:10:51.306 SQL Service MSSQL$PRODUCTION was previously
running, ready for authentication
05/26/2005 21:10:51.306 SQL Agent Service SQLAgent$PRODUCTION was
previously running
05/26/2005 21:10:51.489 User authentication was successful
05/26/2005 21:10:54.787 Attempting to install product: SQLOLAP64|||Hi there:
i am also facing the same problem when i try installing SQL2k SP4 on IA serv
ersWere you able ti fix it. Will appreciate any help.
Kind Regards,
Roshan
From m.htm" target="_blank">http://www.developmentnow.com/g/118...le
m.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com

IA64 SP4 Install Problem

I am having trouble installing SP4 on my IA64. Like the instructions said in
section 1.1 of the help file I have changed it to allow Unsigned drivers to
Silently Succeed. However I am still getting a failure.
On thing to note when I run the following command I get some different
results than the help file say I sould.
SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
SERVERPROPERTY('ProductVersion')
SP3
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit) on
Windows NT 5.2 (Build 3790: )
8.00.818
About a year ago MS and Oracle were working with me to solve a memory leak
issue and I think that may be related to why SP4 wont install but I cant be
sure.
The only hint as to what the error is at the begining of the logfile (See
below).
05/18/2005 08:29:49.910
================================================================================ 05/18/2005 08:29:49.910 Hotfix package launched
05/18/2005 08:29:49.910 Local Computer:
05/18/2005 08:29:49.910 Target Details: SG1
05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:49.910 windir = C:\WINDOWS
05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
05/18/2005 08:29:49.910
05/18/2005 08:29:50.850 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 Product Details:
05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
05/18/2005 08:29:51.110 build = 2039
05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
05/18/2005 08:29:51.110 details = This Service Pack can be applied on all
SQL Server 2000 64-bit features including the relational database engine and
Analysis Services. If you have not done so already, back up the master and
msdb databases and stop all database programs and services before proceeding.
05/18/2005 08:29:51.110 kbarticle = KB884525
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 package = HotFix1
05/18/2005 08:29:51.110 productname = SQLOLAP64
05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Service
Pack 4
05/18/2005 08:29:51.110 splevel = RTM,4
05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:51.110 version = 8
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 File Group Details: MSP
05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress
05/18/2005 08:29:51.110 File Details: sqlrun.msp
05/18/2005 08:29:51.110 lockedfilecheck = 1
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 Instance Details: MSSQLServer
05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
05/18/2005 08:29:51.110 default = TRUE
05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
05/18/2005 08:29:51.110 id = MSSQLServer
05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
SQL Server\MSSQL
05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
Server\MSSQL
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 name = MSSQLServer
05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
05/18/2005 08:29:51.110 productcode = {0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.110 servicename = MSSQLServer
05/18/2005 08:29:51.110 sku = ENTERPRISE
05/18/2005 08:29:51.110 sp = RTM
05/18/2005 08:29:51.110 type = Liberty
05/18/2005 08:29:51.110 version = 8Anybody?
"Jim" wrote:
> I am having trouble installing SP4 on my IA64. Like the instructions said in
> section 1.1 of the help file I have changed it to allow Unsigned drivers to
> Silently Succeed. However I am still getting a failure.
> On thing to note when I run the following command I get some different
> results than the help file say I sould.
> SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
> SERVERPROPERTY('ProductVersion')
> SP3
> Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit) on
> Windows NT 5.2 (Build 3790: )
> 8.00.818
> About a year ago MS and Oracle were working with me to solve a memory leak
> issue and I think that may be related to why SP4 wont install but I cant be
> sure.
> The only hint as to what the error is at the begining of the logfile (See
> below).
> 05/18/2005 08:29:49.910
> ================================================================================> 05/18/2005 08:29:49.910 Hotfix package launched
> 05/18/2005 08:29:49.910 Local Computer:
> 05/18/2005 08:29:49.910 Target Details: SG1
> 05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
> 05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
> 05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:49.910 windir = C:\WINDOWS
> 05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
> 05/18/2005 08:29:49.910
> 05/18/2005 08:29:50.850 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 Product Details:
> 05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
> 05/18/2005 08:29:51.110 build = 2039
> 05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
> 05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
> 05/18/2005 08:29:51.110 details = This Service Pack can be applied on all
> SQL Server 2000 64-bit features including the relational database engine and
> Analysis Services. If you have not done so already, back up the master and
> msdb databases and stop all database programs and services before proceeding.
> 05/18/2005 08:29:51.110 kbarticle = KB884525
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 package = HotFix1
> 05/18/2005 08:29:51.110 productname = SQLOLAP64
> 05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Service
> Pack 4
> 05/18/2005 08:29:51.110 splevel = RTM,4
> 05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:51.110 version = 8
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 File Group Details: MSP
> 05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
> 05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress
> 05/18/2005 08:29:51.110 File Details: sqlrun.msp
> 05/18/2005 08:29:51.110 lockedfilecheck = 1
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
> SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 Instance Details: MSSQLServer
> 05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
> 05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
> 05/18/2005 08:29:51.110 default = TRUE
> 05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
> 05/18/2005 08:29:51.110 id = MSSQLServer
> 05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
> SQL Server\MSSQL
> 05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
> Server\MSSQL
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 name = MSSQLServer
> 05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
> 05/18/2005 08:29:51.110 productcode => {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.110 servicename = MSSQLServer
> 05/18/2005 08:29:51.110 sku = ENTERPRISE
> 05/18/2005 08:29:51.110 sp = RTM
> 05/18/2005 08:29:51.110 type = Liberty
> 05/18/2005 08:29:51.110 version = 8|||Sorry don't have an answer for you. If no one else pipes in you may want to
give MS PSS a call.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly SQL MVP
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:D129328E-93E4-4E2A-BC6B-129B9D7341AE@.microsoft.com...
> Anybody?
> "Jim" wrote:
>> I am having trouble installing SP4 on my IA64. Like the instructions said
>> in
>> section 1.1 of the help file I have changed it to allow Unsigned drivers
>> to
>> Silently Succeed. However I am still getting a failure.
>> On thing to note when I run the following command I get some different
>> results than the help file say I sould.
>> SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
>> SERVERPROPERTY('ProductVersion')
>> SP3
>> Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003
>> 15:32:45
>> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition
>> (64-bit) on
>> Windows NT 5.2 (Build 3790: )
>> 8.00.818
>> About a year ago MS and Oracle were working with me to solve a memory
>> leak
>> issue and I think that may be related to why SP4 wont install but I cant
>> be
>> sure.
>> The only hint as to what the error is at the begining of the logfile (See
>> below).
>> 05/18/2005 08:29:49.910
>> ================================================================================>> 05/18/2005 08:29:49.910 Hotfix package launched
>> 05/18/2005 08:29:49.910 Local Computer:
>> 05/18/2005 08:29:49.910 Target Details: SG1
>> 05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
>> 05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
>> 05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
>> 05/18/2005 08:29:49.910 windir = C:\WINDOWS
>> 05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
>> 05/18/2005 08:29:49.910
>> 05/18/2005 08:29:50.850 The following product instance was disqualified
>> because a parent product instance of the same product code was found:
>> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
>> 05/18/2005 08:29:51.100 The following product instance was disqualified
>> because a parent product instance of the same product code was found:
>> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
>> 05/18/2005 08:29:51.100 Product Details:
>> 05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
>> 05/18/2005 08:29:51.110 build = 2039
>> 05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
>> 05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
>> 05/18/2005 08:29:51.110 details = This Service Pack can be applied on
>> all
>> SQL Server 2000 64-bit features including the relational database engine
>> and
>> Analysis Services. If you have not done so already, back up the master
>> and
>> msdb databases and stop all database programs and services before
>> proceeding.
>> 05/18/2005 08:29:51.110 kbarticle = KB884525
>> 05/18/2005 08:29:51.110 lcid = 1033
>> 05/18/2005 08:29:51.110 package = HotFix1
>> 05/18/2005 08:29:51.110 productname = SQLOLAP64
>> 05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit)
>> Service
>> Pack 4
>> 05/18/2005 08:29:51.110 splevel = RTM,4
>> 05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
>> 05/18/2005 08:29:51.110 version = 8
>> 05/18/2005 08:29:51.110
>> 05/18/2005 08:29:51.110 File Group Details: MSP
>> 05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
>> 05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
>> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039
>> KBNUMBER=KB884525
>> REBOOT=ReallySuppress
>> 05/18/2005 08:29:51.110 File Details: sqlrun.msp
>> 05/18/2005 08:29:51.110 lockedfilecheck = 1
>> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039
>> KBNUMBER=KB884525
>> REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
>> SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
>> MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
>> 05/18/2005 08:29:51.110
>> 05/18/2005 08:29:51.110 Instance Details: MSSQLServer
>> 05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
>> 05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
>> 05/18/2005 08:29:51.110 default = TRUE
>> 05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
>> 05/18/2005 08:29:51.110 id = MSSQLServer
>> 05/18/2005 08:29:51.110 installsqldatadir = C:\Program
>> Files\Microsoft
>> SQL Server\MSSQL
>> 05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft
>> SQL
>> Server\MSSQL
>> 05/18/2005 08:29:51.110 lcid = 1033
>> 05/18/2005 08:29:51.110 name = MSSQLServer
>> 05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
>> 05/18/2005 08:29:51.110 productcode =>> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
>> 05/18/2005 08:29:51.110 servicename = MSSQLServer
>> 05/18/2005 08:29:51.110 sku = ENTERPRISE
>> 05/18/2005 08:29:51.110 sp = RTM
>> 05/18/2005 08:29:51.110 type = Liberty
>> 05/18/2005 08:29:51.110 version = 8|||I'm getting the same error as well. I'm thinking it has something t
do with a previous version of a hotfix that was applied
SELECT @.@.Versio
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 200
15:32:45 Copyright (c) 1988-2003 Microsoft Corporation Enterpris
Edition (64-bit) on Windows NT 5.2 (Build 3790: )
05/26/2005 21:10:33.10
===============================================================================05/26/2005 21:10:33.107 Hotfix package launche
05/26/2005 21:10:33.107 Local Computer
05/26/2005 21:10:33.107 Target Details: OLYMPO
05/26/2005 21:10:33.107 commonfilesdir = C:\Program Files\Commo
File
05/26/2005 21:10:33.107 programfilesdir = C:\Program File
05/26/2005 21:10:33.107 supportdir
\\Pontos\IT\pontos\it\SQL2KSP4\IA6
05/26/2005 21:10:33.107 windir = C:\WINDOW
05/26/2005 21:10:33.107 winsysdir = C:\WINDOWS\system3
05/26/2005 21:10:33.107
05/26/2005 21:10:34.756 The following product instance wa
disqualified because a parent product instance of the same produc
code was found: {0F34966C-4EF4-45AE-B78E-486BEFB71698
05/26/2005 21:10:34.959 The following product instance wa
disqualified because a parent product instance of the same produc
code was found: {FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F
05/26/2005 21:10:34.959 Product Details
05/26/2005 21:10:34.959 INF File Name
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.in
05/26/2005 21:10:34.959 build = 203
05/26/2005 21:10:34.959 description = SQL Server 2000 (64-bit
05/26/2005 21:10:34.959 description2 = Analysis Services 200
(64-bit
05/26/2005 21:10:34.959 details = This Service Pack can be applie
on all SQL Server 2000 64-bit features including the relationa
database engine and Analysis Services. If you have not done s
already, back up the master and msdb databases and stop all databas
programs and services before proceeding
05/26/2005 21:10:34.959 kbarticle = KB88452
05/26/2005 21:10:34.959 lcid = 103
05/26/2005 21:10:34.959 package = HotFix
05/26/2005 21:10:34.959 productname = SQLOLAP6
05/26/2005 21:10:34.959 servicepackname = SQL Server 2000 (64-bit
Service Pack
05/26/2005 21:10:34.959 splevel = RTM,
05/26/2005 21:10:34.959 supportdir
\\Pontos\IT\pontos\it\SQL2KSP4\IA6
05/26/2005 21:10:34.959 version =05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 File Group Details: MS
05/26/2005 21:10:34.959 sourcepath
<SUPPORTDIR>\<PACKAGE>\File
05/26/2005 21:10:34.959 File Details: OverridePreSP4QFE.ms
05/26/2005 21:10:34.959 parameters = SQLBUILD=203
KBNUMBER=KB884525 REBOOT=ReallySuppres
05/26/2005 21:10:34.959 File Details: sqlrun.ms
05/26/2005 21:10:34.959 lockedfilecheck =05/26/2005 21:10:34.959 parameters = SQLBUILD=203
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMD
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 Instance Details: PRODUCTIO
05/26/2005 21:10:34.959 = Software\Microsoft\Microsoft SQ
Server\PRODUCTION\Setu
05/26/2005 21:10:34.959 agentservicename = SQLAgent$PRODUCTIO
05/26/2005 21:10:34.959 hiveregpath = Software\Microsoft\Microsof
SQL Server\PRODUCTIO
05/26/2005 21:10:34.959 id = PRODUCTIO
05/26/2005 21:10:34.959 installsqldatadir = C:\Progra
Files\Microsoft SQL Server\MSSQL$PRODUCTIO
05/26/2005 21:10:34.959 installsqldir = C:\Program Files\Microsof
SQL Server\MSSQL$PRODUCTIO
05/26/2005 21:10:34.959 lcid = 103
05/26/2005 21:10:34.969 name = PRODUCTIO
05/26/2005 21:10:34.969 productcode
{0F34966C-4EF4-45AE-B78E-486BEFB71698
05/26/2005 21:10:34.969 servicename = MSSQL$PRODUCTIO
05/26/2005 21:10:34.969 sku = ENTERPRIS
05/26/2005 21:10:34.969 sp = RT
05/26/2005 21:10:34.969 type = Libert
05/26/2005 21:10:34.969 version =05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWOR
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQ
Server\RMSWORK\Setu
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWOR
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode ={FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = Liberty
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWORK
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWORK
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode ={FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = OLAP
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = SQL Server 2000 (64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: SQL Tools
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\80\Tools
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = SQL Tools
05/26/2005 21:10:34.969 productcode ={0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: OLAPClient
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Common
Files\system\OLE DB
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = OLAPClient
05/26/2005 21:10:34.969 productcode ={FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:51.286 Authenticating user using Windows
Authentication
05/26/2005 21:10:51.306 SQL Service MSSQL$PRODUCTION was previously
running, ready for authentication
05/26/2005 21:10:51.306 SQL Agent Service SQLAgent$PRODUCTION was
previously running
05/26/2005 21:10:51.489 User authentication was successful
05/26/2005 21:10:54.787 Attempting to install product: SQLOLAP64|||Hi there:
i am also facing the same problem when i try installing SQL2k SP4 on IA serversWere you able ti fix it. Will appreciate any help.
Kind Regards,
Rosha
From http://www.developmentnow.com/g/118_2005_5_0_0_524275/IA64-SP4-Install-Problem.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

IA64 bit Performance vs X64 - Update statistics

Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev server i
s
4-way SQL EE x64, 9 GB RAM.
At the end of the day (just prior to midnight) I backup the prod database,
then run update statistics fullscan on 13 tables, 30% scan on 9 other tables
.
Elapsed time is 4.5 hrs.
I can restore the backup just taken on prod over to Dev, run the same update
statistics process from Prod on Dev and the elapsed time on Dev is 3.25 hour
s.
Any ideas that adequately explain the difference in elapsed time?
--
jl"John L" <JohnL@.discussions.microsoft.com> wrote in message
news:FE1A33F1-2EA1-4FF6-8E5B-6D469E398BB9@.microsoft.com...
> Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev server
> is
> 4-way SQL EE x64, 9 GB RAM.
> At the end of the day (just prior to midnight) I backup the prod
> database,
> then run update statistics fullscan on 13 tables, 30% scan on 9 other
> tables.
> Elapsed time is 4.5 hrs.
> I can restore the backup just taken on prod over to Dev, run the same
> update
> statistics process from Prod on Dev and the elapsed time on Dev is 3.25
> hours.
> Any ideas that adequately explain the difference in elapsed time?
Perhaps your dev server is just faster than your production server.
David|||I forgot to mention that the SQL 2000 version for both is SP4.
--
jl
"John L" wrote:

> Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev server
is
> 4-way SQL EE x64, 9 GB RAM.
> At the end of the day (just prior to midnight) I backup the prod database
,
> then run update statistics fullscan on 13 tables, 30% scan on 9 other tabl
es.
> Elapsed time is 4.5 hrs.
> I can restore the backup just taken on prod over to Dev, run the same upda
te
> statistics process from Prod on Dev and the elapsed time on Dev is 3.25 ho
urs.
> Any ideas that adequately explain the difference in elapsed time?
> --
> jl|||Trying to have that make sense to mgt would be a challenge even though I
inherited these servers. The dev box does have faster CPUs than the prod
server. Regrettably mgt listened to someone's notion that the IA64 servers
were "high performers" Maybe that pitch was referring Oracle on Linux :-)
--
jl
"David Browne" wrote:

> "John L" <JohnL@.discussions.microsoft.com> wrote in message
> news:FE1A33F1-2EA1-4FF6-8E5B-6D469E398BB9@.microsoft.com...
> Perhaps your dev server is just faster than your production server.
> David
>
>|||Hi John,
x64 is definitely better than the IA64 processor. But, you cannot really
compare your production numbers to the development numbers because
Production usually has a lot more going on VS your Dev environment. Plus,
you should check your waitstats counters, filestats, and various other
perfmon counters to get a better picture on the difference in performance.
-Shiva
"John L" <JohnL@.discussions.microsoft.com> wrote in message
news:555B3999-CFF7-43BD-80E3-D85B863623E0@.microsoft.com...[vbcol=seagreen]
>I forgot to mention that the SQL 2000 version for both is SP4.
> --
> jl
>
> "John L" wrote:
>|||Shiva:
I might be guilty of some gross oversimplification here. I agree that
production servers theoretically have more going on with them but this an 8-
5
organization meaning that there is no user activity during the time frames i
n
which these maintenance activities occur (on either server). Ruling out
application related traffic generated by end-users, I am left with elapsed
job times. The IA 64 single core box (prod) runs at 4.5 hours ( replace the
single core CPUs with dual core IA 64s and the run time goes up to 6.25
hours), the EMT64T single core box (dev) runs in 3.25 hours.
The EMT64T's are 3600 Mhz CPUS, IA 64 single cores are 1500 Mhz, and the IA
64 dual cores are 1200 Mhz.
My hope with this post was that perhaps there was someone else out there who
had seen something the same or similar in an IA 64 environment. I am gettin
g
the feeling that there were not many who chose to go with SQL 2000 64-bit on
the IA 64 which may be why SQL 2005 is the only MS product certified for IA
64. I fully expect them to drop support for this architecture especially if
the marketplace doesn't ask for it.
There might be a very simple explanation for the observed phenonmenon and
that is simply CPU speed as David Browne has already hinted at.
jl
"Shiva" wrote:

> Hi John,
> x64 is definitely better than the IA64 processor. But, you cannot really
> compare your production numbers to the development numbers because
> Production usually has a lot more going on VS your Dev environment. Plus,
> you should check your waitstats counters, filestats, and various other
> perfmon counters to get a better picture on the difference in performance.
> -Shiva
> "John L" <JohnL@.discussions.microsoft.com> wrote in message
> news:555B3999-CFF7-43BD-80E3-D85B863623E0@.microsoft.com...
>
>|||Hi,
I don't think that updating statistics is the right load to test Itanium2
processor. Based on my experiences when you update statistics, only one
processor is used so it doesn't matter how many cores you have. There is
usually a lot of disk activity involved (depending on amount of RAM) so disk
subsistem has important role here.
I've been testing SQL2000 sp4 IA64 on Itanium2 and found out that when
running simple querries (basic selects...where...) Itanium2 is almost never
faster, usualy is 10-20% slower than Xeon, BUT when running more complex
querries like large complex joins, sorts on large amounts of data, Itanium
is always faster. More complex querry it is and more data is executing on,
faster it is comparing to Xeon. I think that Itanium is best suited for
running large reports, OLAP, complex calculations and so on, when X64 on
Xeons is faster for simple busines applications.
I've also noticed that processor parallelism is much better implemented on
IA64 than running the same load on SQL2000 sp4 x64 or x86. Using 2 Itaniums
relly made execution times for a lot of procedures almost twice as fast than
using one proccesor. When running the same load on Xeons, parallelism made
it actually slower.
I'm begining to test it on SQL2005. So far, a lot of procedures are faster
then on SQL2000.....
Those are my experiences so far...
Tom
"John L" <JohnL@.discussions.microsoft.com> wrote in message
news:12FCED74-D78D-4912-A81F-13732A833316@.microsoft.com...[vbcol=seagreen]
> Shiva:
> I might be guilty of some gross oversimplification here. I agree that
> production servers theoretically have more going on with them but this an
> 8-5
> organization meaning that there is no user activity during the time frames
> in
> which these maintenance activities occur (on either server). Ruling out
> application related traffic generated by end-users, I am left with elapsed
> job times. The IA 64 single core box (prod) runs at 4.5 hours ( replace
> the
> single core CPUs with dual core IA 64s and the run time goes up to 6.25
> hours), the EMT64T single core box (dev) runs in 3.25 hours.
> The EMT64T's are 3600 Mhz CPUS, IA 64 single cores are 1500 Mhz, and the
> IA
> 64 dual cores are 1200 Mhz.
> My hope with this post was that perhaps there was someone else out there
> who
> had seen something the same or similar in an IA 64 environment. I am
> getting
> the feeling that there were not many who chose to go with SQL 2000 64-bit
> on
> the IA 64 which may be why SQL 2005 is the only MS product certified for
> IA
> 64. I fully expect them to drop support for this architecture especially
> if
> the marketplace doesn't ask for it.
> There might be a very simple explanation for the observed phenonmenon and
> that is simply CPU speed as David Browne has already hinted at.
> --
> jl
>
> "Shiva" wrote:
>|||Tom:
A funny thing about our IA64 experience is that our h/w mgr jumped out and
bought dual core CPUs for the server. After installation the UPDATE STATS
took 1.25 hrs longer than with the single core IA64 CPUs.
Thanks for sharing your experience, this is exactly the sort of feedback
that I have been seeking.
jl
"Tom" wrote:

> Hi,
> I don't think that updating statistics is the right load to test Itanium2
> processor. Based on my experiences when you update statistics, only one
> processor is used so it doesn't matter how many cores you have. There is
> usually a lot of disk activity involved (depending on amount of RAM) so di
sk
> subsistem has important role here.
> I've been testing SQL2000 sp4 IA64 on Itanium2 and found out that when
> running simple querries (basic selects...where...) Itanium2 is almost nev
er
> faster, usualy is 10-20% slower than Xeon, BUT when running more complex
> querries like large complex joins, sorts on large amounts of data, Itanium
> is always faster. More complex querry it is and more data is executing on,
> faster it is comparing to Xeon. I think that Itanium is best suited for
> running large reports, OLAP, complex calculations and so on, when X64 on
> Xeons is faster for simple busines applications.
> I've also noticed that processor parallelism is much better implemented on
> IA64 than running the same load on SQL2000 sp4 x64 or x86. Using 2 Itanium
s
> relly made execution times for a lot of procedures almost twice as fast th
an
> using one proccesor. When running the same load on Xeons, parallelism made
> it actually slower.
> I'm begining to test it on SQL2005. So far, a lot of procedures are faster
> then on SQL2000.....
> Those are my experiences so far...
> Tom
>
>
> "John L" <JohnL@.discussions.microsoft.com> wrote in message
> news:12FCED74-D78D-4912-A81F-13732A833316@.microsoft.com...
>
>

IA64 bit Performance vs X64 - Update statistics

Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev server is
4-way SQL EE x64, 9 GB RAM.
At the end of the day (just prior to midnight) I backup the prod database,
then run update statistics fullscan on 13 tables, 30% scan on 9 other tables.
Elapsed time is 4.5 hrs.
I can restore the backup just taken on prod over to Dev, run the same update
statistics process from Prod on Dev and the elapsed time on Dev is 3.25 hours.
Any ideas that adequately explain the difference in elapsed time?
--
jl"John L" <JohnL@.discussions.microsoft.com> wrote in message
news:FE1A33F1-2EA1-4FF6-8E5B-6D469E398BB9@.microsoft.com...
> Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev server
> is
> 4-way SQL EE x64, 9 GB RAM.
> At the end of the day (just prior to midnight) I backup the prod
> database,
> then run update statistics fullscan on 13 tables, 30% scan on 9 other
> tables.
> Elapsed time is 4.5 hrs.
> I can restore the backup just taken on prod over to Dev, run the same
> update
> statistics process from Prod on Dev and the elapsed time on Dev is 3.25
> hours.
> Any ideas that adequately explain the difference in elapsed time?
Perhaps your dev server is just faster than your production server.
David|||I forgot to mention that the SQL 2000 version for both is SP4.
--
jl
"John L" wrote:
> Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev server is
> 4-way SQL EE x64, 9 GB RAM.
> At the end of the day (just prior to midnight) I backup the prod database,
> then run update statistics fullscan on 13 tables, 30% scan on 9 other tables.
> Elapsed time is 4.5 hrs.
> I can restore the backup just taken on prod over to Dev, run the same update
> statistics process from Prod on Dev and the elapsed time on Dev is 3.25 hours.
> Any ideas that adequately explain the difference in elapsed time?
> --
> jl|||Trying to have that make sense to mgt would be a challenge even though I
inherited these servers. The dev box does have faster CPUs than the prod
server. Regrettably mgt listened to someone's notion that the IA64 servers
were "high performers" Maybe that pitch was referring Oracle on Linux :-)
--
jl
"David Browne" wrote:
> "John L" <JohnL@.discussions.microsoft.com> wrote in message
> news:FE1A33F1-2EA1-4FF6-8E5B-6D469E398BB9@.microsoft.com...
> > Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev server
> > is
> > 4-way SQL EE x64, 9 GB RAM.
> >
> > At the end of the day (just prior to midnight) I backup the prod
> > database,
> > then run update statistics fullscan on 13 tables, 30% scan on 9 other
> > tables.
> > Elapsed time is 4.5 hrs.
> >
> > I can restore the backup just taken on prod over to Dev, run the same
> > update
> > statistics process from Prod on Dev and the elapsed time on Dev is 3.25
> > hours.
> >
> > Any ideas that adequately explain the difference in elapsed time?
> Perhaps your dev server is just faster than your production server.
> David
>
>|||Hi John,
x64 is definitely better than the IA64 processor. But, you cannot really
compare your production numbers to the development numbers because
Production usually has a lot more going on VS your Dev environment. Plus,
you should check your waitstats counters, filestats, and various other
perfmon counters to get a better picture on the difference in performance.
-Shiva
"John L" <JohnL@.discussions.microsoft.com> wrote in message
news:555B3999-CFF7-43BD-80E3-D85B863623E0@.microsoft.com...
>I forgot to mention that the SQL 2000 version for both is SP4.
> --
> jl
>
> "John L" wrote:
>> Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev
>> server is
>> 4-way SQL EE x64, 9 GB RAM.
>> At the end of the day (just prior to midnight) I backup the prod
>> database,
>> then run update statistics fullscan on 13 tables, 30% scan on 9 other
>> tables.
>> Elapsed time is 4.5 hrs.
>> I can restore the backup just taken on prod over to Dev, run the same
>> update
>> statistics process from Prod on Dev and the elapsed time on Dev is 3.25
>> hours.
>> Any ideas that adequately explain the difference in elapsed time?
>> --
>> jl|||Shiva:
I might be guilty of some gross oversimplification here. I agree that
production servers theoretically have more going on with them but this an 8-5
organization meaning that there is no user activity during the time frames in
which these maintenance activities occur (on either server). Ruling out
application related traffic generated by end-users, I am left with elapsed
job times. The IA 64 single core box (prod) runs at 4.5 hours ( replace the
single core CPUs with dual core IA 64s and the run time goes up to 6.25
hours), the EMT64T single core box (dev) runs in 3.25 hours.
The EMT64T's are 3600 Mhz CPUS, IA 64 single cores are 1500 Mhz, and the IA
64 dual cores are 1200 Mhz.
My hope with this post was that perhaps there was someone else out there who
had seen something the same or similar in an IA 64 environment. I am getting
the feeling that there were not many who chose to go with SQL 2000 64-bit on
the IA 64 which may be why SQL 2005 is the only MS product certified for IA
64. I fully expect them to drop support for this architecture especially if
the marketplace doesn't ask for it.
There might be a very simple explanation for the observed phenonmenon and
that is simply CPU speed as David Browne has already hinted at.
--
jl
"Shiva" wrote:
> Hi John,
> x64 is definitely better than the IA64 processor. But, you cannot really
> compare your production numbers to the development numbers because
> Production usually has a lot more going on VS your Dev environment. Plus,
> you should check your waitstats counters, filestats, and various other
> perfmon counters to get a better picture on the difference in performance.
> -Shiva
> "John L" <JohnL@.discussions.microsoft.com> wrote in message
> news:555B3999-CFF7-43BD-80E3-D85B863623E0@.microsoft.com...
> >I forgot to mention that the SQL 2000 version for both is SP4.
> > --
> > jl
> >
> >
> > "John L" wrote:
> >
> >> Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev
> >> server is
> >> 4-way SQL EE x64, 9 GB RAM.
> >>
> >> At the end of the day (just prior to midnight) I backup the prod
> >> database,
> >> then run update statistics fullscan on 13 tables, 30% scan on 9 other
> >> tables.
> >> Elapsed time is 4.5 hrs.
> >>
> >> I can restore the backup just taken on prod over to Dev, run the same
> >> update
> >> statistics process from Prod on Dev and the elapsed time on Dev is 3.25
> >> hours.
> >>
> >> Any ideas that adequately explain the difference in elapsed time?
> >> --
> >> jl
>
>|||Hi,
I don't think that updating statistics is the right load to test Itanium2
processor. Based on my experiences when you update statistics, only one
processor is used so it doesn't matter how many cores you have. There is
usually a lot of disk activity involved (depending on amount of RAM) so disk
subsistem has important role here.
I've been testing SQL2000 sp4 IA64 on Itanium2 and found out that when
running simple querries (basic selects...where...) Itanium2 is almost never
faster, usualy is 10-20% slower than Xeon, BUT when running more complex
querries like large complex joins, sorts on large amounts of data, Itanium
is always faster. More complex querry it is and more data is executing on,
faster it is comparing to Xeon. I think that Itanium is best suited for
running large reports, OLAP, complex calculations and so on, when X64 on
Xeons is faster for simple busines applications.
I've also noticed that processor parallelism is much better implemented on
IA64 than running the same load on SQL2000 sp4 x64 or x86. Using 2 Itaniums
relly made execution times for a lot of procedures almost twice as fast than
using one proccesor. When running the same load on Xeons, parallelism made
it actually slower.
I'm begining to test it on SQL2005. So far, a lot of procedures are faster
then on SQL2000.....
Those are my experiences so far...
Tom
"John L" <JohnL@.discussions.microsoft.com> wrote in message
news:12FCED74-D78D-4912-A81F-13732A833316@.microsoft.com...
> Shiva:
> I might be guilty of some gross oversimplification here. I agree that
> production servers theoretically have more going on with them but this an
> 8-5
> organization meaning that there is no user activity during the time frames
> in
> which these maintenance activities occur (on either server). Ruling out
> application related traffic generated by end-users, I am left with elapsed
> job times. The IA 64 single core box (prod) runs at 4.5 hours ( replace
> the
> single core CPUs with dual core IA 64s and the run time goes up to 6.25
> hours), the EMT64T single core box (dev) runs in 3.25 hours.
> The EMT64T's are 3600 Mhz CPUS, IA 64 single cores are 1500 Mhz, and the
> IA
> 64 dual cores are 1200 Mhz.
> My hope with this post was that perhaps there was someone else out there
> who
> had seen something the same or similar in an IA 64 environment. I am
> getting
> the feeling that there were not many who chose to go with SQL 2000 64-bit
> on
> the IA 64 which may be why SQL 2005 is the only MS product certified for
> IA
> 64. I fully expect them to drop support for this architecture especially
> if
> the marketplace doesn't ask for it.
> There might be a very simple explanation for the observed phenonmenon and
> that is simply CPU speed as David Browne has already hinted at.
> --
> jl
>
> "Shiva" wrote:
>> Hi John,
>> x64 is definitely better than the IA64 processor. But, you cannot really
>> compare your production numbers to the development numbers because
>> Production usually has a lot more going on VS your Dev environment. Plus,
>> you should check your waitstats counters, filestats, and various other
>> perfmon counters to get a better picture on the difference in
>> performance.
>> -Shiva
>> "John L" <JohnL@.discussions.microsoft.com> wrote in message
>> news:555B3999-CFF7-43BD-80E3-D85B863623E0@.microsoft.com...
>> >I forgot to mention that the SQL 2000 version for both is SP4.
>> > --
>> > jl
>> >
>> >
>> > "John L" wrote:
>> >
>> >> Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev
>> >> server is
>> >> 4-way SQL EE x64, 9 GB RAM.
>> >>
>> >> At the end of the day (just prior to midnight) I backup the prod
>> >> database,
>> >> then run update statistics fullscan on 13 tables, 30% scan on 9 other
>> >> tables.
>> >> Elapsed time is 4.5 hrs.
>> >>
>> >> I can restore the backup just taken on prod over to Dev, run the same
>> >> update
>> >> statistics process from Prod on Dev and the elapsed time on Dev is
>> >> 3.25
>> >> hours.
>> >>
>> >> Any ideas that adequately explain the difference in elapsed time?
>> >> --
>> >> jl
>>|||Tom:
A funny thing about our IA64 experience is that our h/w mgr jumped out and
bought dual core CPUs for the server. After installation the UPDATE STATS
took 1.25 hrs longer than with the single core IA64 CPUs.
Thanks for sharing your experience, this is exactly the sort of feedback
that I have been seeking.
--
jl
"Tom" wrote:
> Hi,
> I don't think that updating statistics is the right load to test Itanium2
> processor. Based on my experiences when you update statistics, only one
> processor is used so it doesn't matter how many cores you have. There is
> usually a lot of disk activity involved (depending on amount of RAM) so disk
> subsistem has important role here.
> I've been testing SQL2000 sp4 IA64 on Itanium2 and found out that when
> running simple querries (basic selects...where...) Itanium2 is almost never
> faster, usualy is 10-20% slower than Xeon, BUT when running more complex
> querries like large complex joins, sorts on large amounts of data, Itanium
> is always faster. More complex querry it is and more data is executing on,
> faster it is comparing to Xeon. I think that Itanium is best suited for
> running large reports, OLAP, complex calculations and so on, when X64 on
> Xeons is faster for simple busines applications.
> I've also noticed that processor parallelism is much better implemented on
> IA64 than running the same load on SQL2000 sp4 x64 or x86. Using 2 Itaniums
> relly made execution times for a lot of procedures almost twice as fast than
> using one proccesor. When running the same load on Xeons, parallelism made
> it actually slower.
> I'm begining to test it on SQL2005. So far, a lot of procedures are faster
> then on SQL2000.....
> Those are my experiences so far...
> Tom
>
>
> "John L" <JohnL@.discussions.microsoft.com> wrote in message
> news:12FCED74-D78D-4912-A81F-13732A833316@.microsoft.com...
> > Shiva:
> >
> > I might be guilty of some gross oversimplification here. I agree that
> > production servers theoretically have more going on with them but this an
> > 8-5
> > organization meaning that there is no user activity during the time frames
> > in
> > which these maintenance activities occur (on either server). Ruling out
> > application related traffic generated by end-users, I am left with elapsed
> > job times. The IA 64 single core box (prod) runs at 4.5 hours ( replace
> > the
> > single core CPUs with dual core IA 64s and the run time goes up to 6.25
> > hours), the EMT64T single core box (dev) runs in 3.25 hours.
> >
> > The EMT64T's are 3600 Mhz CPUS, IA 64 single cores are 1500 Mhz, and the
> > IA
> > 64 dual cores are 1200 Mhz.
> >
> > My hope with this post was that perhaps there was someone else out there
> > who
> > had seen something the same or similar in an IA 64 environment. I am
> > getting
> > the feeling that there were not many who chose to go with SQL 2000 64-bit
> > on
> > the IA 64 which may be why SQL 2005 is the only MS product certified for
> > IA
> > 64. I fully expect them to drop support for this architecture especially
> > if
> > the marketplace doesn't ask for it.
> >
> > There might be a very simple explanation for the observed phenonmenon and
> > that is simply CPU speed as David Browne has already hinted at.
> >
> > --
> > jl
> >
> >
> > "Shiva" wrote:
> >
> >> Hi John,
> >>
> >> x64 is definitely better than the IA64 processor. But, you cannot really
> >> compare your production numbers to the development numbers because
> >> Production usually has a lot more going on VS your Dev environment. Plus,
> >> you should check your waitstats counters, filestats, and various other
> >> perfmon counters to get a better picture on the difference in
> >> performance.
> >>
> >> -Shiva
> >>
> >> "John L" <JohnL@.discussions.microsoft.com> wrote in message
> >> news:555B3999-CFF7-43BD-80E3-D85B863623E0@.microsoft.com...
> >> >I forgot to mention that the SQL 2000 version for both is SP4.
> >> > --
> >> > jl
> >> >
> >> >
> >> > "John L" wrote:
> >> >
> >> >> Prod server is a 4-way IA64 running SQL EE(64-bit), 32 GB RAM. Dev
> >> >> server is
> >> >> 4-way SQL EE x64, 9 GB RAM.
> >> >>
> >> >> At the end of the day (just prior to midnight) I backup the prod
> >> >> database,
> >> >> then run update statistics fullscan on 13 tables, 30% scan on 9 other
> >> >> tables.
> >> >> Elapsed time is 4.5 hrs.
> >> >>
> >> >> I can restore the backup just taken on prod over to Dev, run the same
> >> >> update
> >> >> statistics process from Prod on Dev and the elapsed time on Dev is
> >> >> 3.25
> >> >> hours.
> >> >>
> >> >> Any ideas that adequately explain the difference in elapsed time?
> >> >> --
> >> >> jl
> >>
> >>
> >>
>
>sql