![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, Generally, are there any potential problems with installing Analysis Services on a clustered server that already has SQLServer 2000 installed on multiple virtual servers? I mean in terms of cross-dependencies between AS2000 and SS2000 with respect to their functionalities or Service Pack requirements, or even any impacts on client-side MDAC? Are there any good resources covering this? In more detail... and where it gets tricky... and apologies for the length but you will appreciate the need for detail... I work in a validated environment. We run SS2000 SP1 on the production cluster and SS2000 SP1 on a 2nd cluster (the 2nd cluster contains 2 validation instances and 1 reporting instance). Both production and validation would have to be on the same service pack because it is likely that the re-validation effort required would preclude an upgrade. [For those of you who are unfamiliar with the term validation... Validation is essentially the same as testing, but testing in the context of a regulated US FDA formal, documented testing regime which medical device and pharmaceutical companies must adhere to. This puts a very large and expensive burden on project lifecycles and means that every change to the software or environment must be assessed as to its impact on the quality of the system. As you can imagine, nothing gets changed unless there is a very, very high level of confidence that everything will be ok.] Specifically.... I have a production instance on 1 cluster. On a second cluster I have 2 validation instances and 1 reporting instance (hence AS2000). The applications are all VB6 client/server architecture (although AS2000 will be a mixture of web and client MMC consoles) Both machines are 2 node, active/passive clusters running Windows 2003 Server with SAN storage. The production cluster has 1 virtual server with a SS2000 instance running on it. The second cluster has 3 virtual servers which each have their own instance (i.e. separate binaries on the E:\, F:\ and G:\ drives of the underlying single OS.) There are SS2000 files on the C:\ drive which look like they might be shared - not sure but they could also be the client tools for SS2000 (any ideas?). This is the output from the @@version command which is identical on each of the instances: "Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)" Is it possible to: 1. Install separate service packs on the different instances on the second cluster, i.e. keeping the 2 validation instances on SP1 and moving the reporting instance to SP4. Are there any side-effects to common files, regedit or uninstalling service packs complaining about shared DLLs on C:\ drive? 2. After installing AS2000 (SP?) on the reporting virtual server on the second cluster, would the presence of AS2000 on the second cluster compromise in any way (i) the operation of the validation instances, (ii) force an upgrade to a higher service pack on SS2000 the validation instance, (iii) interfere with the way in which client MDAC DLLs communicate with the validation instance or (iv) compromise an uninstall scenario? What makes me wonder about this is there there are a lot of components and pre-requisites for AS2000. I successfully installed it on my own PC (XP with MSDE - command line install) and found that the install was quite intricate. The question is if the installs clearly and cleanly operate independently of each other in a clustered/virtual server context. Any help would be very much appreciated. Regards Liam |
#3
| |||
| |||
|
|
From this posting it looks like the answer might be yes... this person had a problem installing SP4 on a multi-instance 2003 server... |
#4
| |||
| |||
|
|
Yes, you are right... SP4 and yes, that hotfix is important especially after we ordered extra RAM for the machine to bring it up to 8GB!! SS2000 SP4 simplifies the whole thing... the question now is can the installation of AS2000 affect in any way the installed SS2000 SP4 files that reside outside of the virtual servers , i.e. on the C:\ with the OS. I attach the directory listing? (BTW, I am assuming that any SS2000 files inside the virtual servers will not be affected. Is this correct? ) From this posting it looks like the answer might be yes... this person had a problem installing SP4 on a multi-instance 2003 server... http://groups.google.ie/group/micros...ec03c19d001c99 It wouldn't let him write to a shared file that is listed below (msxmlsql.rll) during the application of SP4 while the second instance was running. What was it trying to write? Would the same happen with AS2000 install or the hotfix? This is precisely what I am trying to figure out. What is the impact of whatever is written? This is the current directory for the listing: C:\Program Files\Microsoft SQL Server Do anything here stand out? (We don't use replication or log shipping - just backup log/copy/restore jobs) Thanks for your help... Liam ..\80 ..\80\COM ..\80\Shared ..\80\Tools ..\80\COM\1033 ..\80\COM\distrib.exe ..\80\COM\dw15.exe ..\80\COM\impprov.dll ..\80\COM\logread.exe ..\80\COM\mergetxt.dll ..\80\COM\msgprox.dll ..\80\COM\Other ..\80\COM\qrdrsvc.exe ..\80\COM\rdistcom.dll ..\80\COM\replagnt.dll ..\80\COM\repldist.dll ..\80\COM\repldp.dll ..\80\COM\repldsui.dll ..\80\COM\repldts.dll ..\80\COM\replerrx.dll ..\80\COM\replmerg.exe ..\80\COM\replprov.dll ..\80\COM\replprox.dll ..\80\COM\replrec.dll ..\80\COM\replsub.dll ..\80\COM\replsync.dll ..\80\COM\Resources ..\80\COM\rinitcom.dll ..\80\COM\snapshot.exe ..\80\COM\spresolv.dll ..\80\COM\sqldistx.dll ..\80\COM\sqldumper.exe ..\80\COM\sqlfth75.dll ..\80\COM\sqlinitx.dll ..\80\COM\sqlmergx.dll ..\80\COM\sqlresld.dll ..\80\COM\sqlvdi.dll ..\80\COM\ssradd.dll ..\80\COM\ssravg.dll ..\80\COM\ssrdown.dll ..\80\COM\ssrmax.dll ..\80\COM\ssrmin.dll ..\80\COM\ssrpub.dll ..\80\COM\ssrup.dll ..\80\COM\1033\dwintl.dll ..\80\COM\Other\dwintl.dll ..\80\COM\Resources\1033 ..\80\COM\Resources\1033\replres.rll ..\80\Shared\msxmlsql.dll ..\80\Shared\Resources ..\80\Shared\Resources\1033 ..\80\Shared\Resources\1033\msxmlsql.rll ..\80\Tools\Binn ..\80\Tools\Books ..\80\Tools\DevTools ..\80\Tools\HTML ..\80\Tools\Install ..\80\Tools\Scripts ..\80\Tools\sqlsun.dll ..\80\Tools\sqlsunin.ini ..\80\Tools\Templates ..\80\Tools\Uninst.isu ..\80\Tools\Binn\autoplt.dll ..\80\Tools\Binn\autowiz.dll ..\80\Tools\Binn\axscphst.dll ..\80\Tools\Binn\bcp.exe ..\80\Tools\Binn\cdw.exe ..\80\Tools\Binn\cdwtasks.dll ..\80\Tools\Binn\cdwtskui.dll ..\80\Tools\Binn\cnfgsvr.exe ..\80\Tools\Binn\cnfgsvr.ini ..\80\Tools\Binn\colctrl.dll ..\80\Tools\Binn\comnevnt.dll ..\80\Tools\Binn\ctasksui.dll ..\80\Tools\Binn\custtask.dll ..\80\Tools\Binn\dcomscm.exe ..\80\Tools\Binn\dtsffile.dll ..\80\Tools\Binn\dtspkg.dll ..\80\Tools\Binn\dtspump.dll ..\80\Tools\Binn\dtsrun.exe ..\80\Tools\Binn\dtsrunui.exe ..\80\Tools\Binn\dtsui.dll ..\80\Tools\Binn\dtswiz.dll ..\80\Tools\Binn\dtswiz.exe ..\80\Tools\Binn\hhsetup.dll ..\80\Tools\Binn\isql.exe ..\80\Tools\Binn\isqlw.exe ..\80\Tools\Binn\itwiz.exe ..\80\Tools\Binn\objmgr.dll ..\80\Tools\Binn\objmgr80.xml ..\80\Tools\Binn\odbccmpt.exe ..\80\Tools\Binn\osql.exe ..\80\Tools\Binn\pfclnt80.dll ..\80\Tools\Binn\pfutil80.dll ..\80\Tools\Binn\profiler.exe ..\80\Tools\Binn\psdcscm.dll ..\80\Tools\Binn\rebuildm.exe ..\80\Tools\Binn\replmon.pmc ..\80\Tools\Binn\Resources ..\80\Tools\Binn\scm.exe ..\80\Tools\Binn\sdiclnt.dll ..\80\Tools\Binn\semcomn.dll ..\80\Tools\Binn\semcros.dll ..\80\Tools\Binn\semdll.dll ..\80\Tools\Binn\semdts.dll ..\80\Tools\Binn\semexec.dll ..\80\Tools\Binn\semmap.dll ..\80\Tools\Binn\semnt.dll ..\80\Tools\Binn\semobj.dll ..\80\Tools\Binn\semrepl.dll ..\80\Tools\Binn\semsfc.dll ..\80\Tools\Binn\semsys.dll ..\80\Tools\Binn\semwebwz.dll ..\80\Tools\Binn\semwiz.dll ..\80\Tools\Binn\sqdedev.dll ..\80\Tools\Binn\sql iis admin.msc ..\80\Tools\Binn\SQL Server Enterprise Manager.MSC ..\80\Tools\Binn\sqladhlp.exe ..\80\Tools\Binn\sqlbrows.cnt ..\80\Tools\Binn\sqlbrows.hlp ..\80\Tools\Binn\sqldmo.dll ..\80\Tools\Binn\sqldmo80.cnt ..\80\Tools\Binn\sqldmo80.hlp ..\80\Tools\Binn\sqldts80.cnt ..\80\Tools\Binn\sqldts80.hlp ..\80\Tools\Binn\sqlftwiz.dll ..\80\Tools\Binn\sqlftwiz.exe ..\80\Tools\Binn\sqlgui.dll ..\80\Tools\Binn\sqllex.dll ..\80\Tools\Binn\sqlmangr.exe ..\80\Tools\Binn\sqlmmc.dll ..\80\Tools\Binn\sqlmmcem.chm ..\80\Tools\Binn\sqlmmcii.chm ..\80\Tools\Binn\sqlns.dll ..\80\Tools\Binn\sqlns80.cnt ..\80\Tools\Binn\sqlns80.hlp ..\80\Tools\Binn\sqlqry.dll ..\80\Tools\Binn\sqlresld.dll ..\80\Tools\Binn\sqlslic.cpl ..\80\Tools\Binn\sqlsui.dll ..\80\Tools\Binn\sqlsun.dll ..\80\Tools\Binn\sqlsvc.dll ..\80\Tools\Binn\sqlvdir.dll ..\80\Tools\Binn\stardds.dll ..\80\Tools\Binn\svrnetcn.dll ..\80\Tools\Binn\svrnetcn.exe ..\80\Tools\Binn\uncol.exe ..\80\Tools\Binn\w95scm.dll ..\80\Tools\Binn\wiztrace.exe ..\80\Tools\Binn\Resources\1033 ..\80\Tools\Binn\Resources\1033\autoplt.rll ..\80\Tools\Binn\Resources\1033\autowiz.rll ..\80\Tools\Binn\Resources\1033\axscphst.rll ..\80\Tools\Binn\Resources\1033\bcp.rll ..\80\Tools\Binn\Resources\1033\cdw.rll ..\80\Tools\Binn\Resources\1033\cdwtasks.rll ..\80\Tools\Binn\Resources\1033\cdwtskui.rll ..\80\Tools\Binn\Resources\1033\ctasksui.rll ..\80\Tools\Binn\Resources\1033\custtask.rll ..\80\Tools\Binn\Resources\1033\dtsffile.rll ..\80\Tools\Binn\Resources\1033\dtspkg.rll ..\80\Tools\Binn\Resources\1033\dtspump.rll ..\80\Tools\Binn\Resources\1033\dtsrun.rll ..\80\Tools\Binn\Resources\1033\dtsrunui.rll ..\80\Tools\Binn\Resources\1033\dtsui.rll ..\80\Tools\Binn\Resources\1033\dtswiz.rll ..\80\Tools\Binn\Resources\1033\isqlw.rll ..\80\Tools\Binn\Resources\1033\itwiz.rll ..\80\Tools\Binn\Resources\1033\objmgr.rll ..\80\Tools\Binn\Resources\1033\pfclnt80.rll ..\80\Tools\Binn\Resources\1033\pfutil80.rll ..\80\Tools\Binn\Resources\1033\profiler.rll ..\80\Tools\Binn\Resources\1033\rebuildm.rll ..\80\Tools\Binn\Resources\1033\semcomn.rll ..\80\Tools\Binn\Resources\1033\semcros.rll ..\80\Tools\Binn\Resources\1033\semdll.rll ..\80\Tools\Binn\Resources\1033\semdts.rll ..\80\Tools\Binn\Resources\1033\semexec.rll ..\80\Tools\Binn\Resources\1033\semmap.rll ..\80\Tools\Binn\Resources\1033\semnt.rll ..\80\Tools\Binn\Resources\1033\semobj.rll ..\80\Tools\Binn\Resources\1033\semrepl.rll ..\80\Tools\Binn\Resources\1033\semsfc.rll ..\80\Tools\Binn\Resources\1033\semsys.rll ..\80\Tools\Binn\Resources\1033\semwebwz.rll ..\80\Tools\Binn\Resources\1033\semwiz.rll ..\80\Tools\Binn\Resources\1033\sqladevn.rll ..\80\Tools\Binn\Resources\1033\sqldmo.rll ..\80\Tools\Binn\Resources\1033\sqlftwiz.rll ..\80\Tools\Binn\Resources\1033\sqlgui.rll ..\80\Tools\Binn\Resources\1033\sqlmangr.rll ..\80\Tools\Binn\Resources\1033\sqlmmc.rll ..\80\Tools\Binn\Resources\1033\sqlns.rll ..\80\Tools\Binn\Resources\1033\sqlqry.rll ..\80\Tools\Binn\Resources\1033\sqlsui.rll ..\80\Tools\Binn\Resources\1033\sqlsvc.rll ..\80\Tools\Binn\Resources\1033\sqlvdir.rll ..\80\Tools\Binn\Resources\1033\svrnetcn.rll ..\80\Tools\Binn\Resources\1033\wiztrace.rll ..\80\Tools\Books\acdata.chi ..\80\Tools\Books\acdata.chm ..\80\Tools\Books\adminsql.chi ..\80\Tools\Books\adminsql.chm ..\80\Tools\Books\adosql.chi ..\80\Tools\Books\adosql.chm ..\80\Tools\Books\architec.chi ..\80\Tools\Books\architec.chm ..\80\Tools\Books\bldgapps.chi ..\80\Tools\Books\bldgapps.chm ..\80\Tools\Books\coprompt.chi ..\80\Tools\Books\coprompt.chm ..\80\Tools\Books\createdb.chi ..\80\Tools\Books\createdb.chm ..\80\Tools\Books\createdw.chi ..\80\Tools\Books\createdw.chm ..\80\Tools\Books\dblibc.chi ..\80\Tools\Books\dblibc.chm ..\80\Tools\Books\dbmigwiz.chi ..\80\Tools\Books\dbmigwiz.chm ..\80\Tools\Books\dbmntwiz.chi ..\80\Tools\Books\dbmntwiz.chm ..\80\Tools\Books\distsql.chi ..\80\Tools\Books\distsql.chm ..\80\Tools\Books\dtsdsgnr.chi ..\80\Tools\Books\dtsdsgnr.chm ..\80\Tools\Books\dtsprog.chi ..\80\Tools\Books\dtsprog.chm ..\80\Tools\Books\dtsrunui.chi ..\80\Tools\Books\dtsrunui.chm ..\80\Tools\Books\dtssql.chi ..\80\Tools\Books\dtssql.chm ..\80\Tools\Books\dtswizrd.chi ..\80\Tools\Books\dtswizrd.chm ..\80\Tools\Books\entrmgr.chi ..\80\Tools\Books\entrmgr.chm ..\80\Tools\Books\eqbol.chi ..\80\Tools\Books\eqbol.chm ..\80\Tools\Books\esqlforc.chi ..\80\Tools\Books\esqlforc.chm ..\80\Tools\Books\fulltxt.chi ..\80\Tools\Books\fulltxt.chm ..\80\Tools\Books\glossary.chi ..\80\Tools\Books\glossary.chm ..\80\Tools\Books\hlpview.chi ..\80\Tools\Books\hlpview.chm ..\80\Tools\Books\howtosql.chi ..\80\Tools\Books\howtosql.chm ..\80\Tools\Books\iisadmin.chi ..\80\Tools\Books\iisadmin.chm ..\80\Tools\Books\indextun.chi ..\80\Tools\Books\indextun.chm ..\80\Tools\Books\instsql.chi ..\80\Tools\Books\instsql.chm ..\80\Tools\Books\mdacxml.chi ..\80\Tools\Books\mdacxml.chm ..\80\Tools\Books\netconf.chi ..\80\Tools\Books\netconf.chm ..\80\Tools\Books\odbcsql.chi ..\80\Tools\Books\odbcsql.chm ..\80\Tools\Books\odssql.chi ..\80\Tools\Books\odssql.chm ..\80\Tools\Books\olapdmad.chi ..\80\Tools\Books\olapdmad.chm ..\80\Tools\Books\olapdmpr.chi ..\80\Tools\Books\olapdmpr.chm ..\80\Tools\Books\oledbsql.chi ..\80\Tools\Books\oledbsql.chm ..\80\Tools\Books\optimsql.chi ..\80\Tools\Books\optimsql.chm ..\80\Tools\Books\profiler.chi |
#5
| |||
| |||
|
|
Hi Liam The files listed are not a full install, on the other drives you will have copies of sqlserve.exe! As your Database engine is already on SP4 I am not sure if your original question is an issue? The problem may occur if you have two live instances running on the same server, failing over so you are only upgrading the one live on that server would (hopefully) avoid this. Installing AS SP 4 requires you to failover to the given node before the upgrade see http://tinyurl.com/ycsjxc John |
#6
| |||
| |||
|
|
Hi John, Yes the full installs are on another drive and are ringfenced by the virtual server. I am not really worried about them. It is the shared files listed previously that I am concerned about. Why should 2 live instances running on the server interfere with each other when installing service packs or AS or whatever? Is this related to http://tinyurl.com/y5attu Why is the upgrade trying to access the file C:\Program Files\Sql Server\80\Shared\msxmlsql.dll? What is it writing to that file? Regards Liam John Bell wrote: Hi Liam The files listed are not a full install, on the other drives you will have copies of sqlserve.exe! As your Database engine is already on SP4 I am not sure if your original question is an issue? The problem may occur if you have two live instances running on the same server, failing over so you are only upgrading the one live on that server would (hopefully) avoid this. Installing AS SP 4 requires you to failover to the given node before the upgrade see http://tinyurl.com/ycsjxc John |
![]() |
| Thread Tools | |
| Display Modes | |
| |