Re: Semnt.dll version after new instance installed
From: Arhontis (arhontis_at_yahoo.com)
Date: 02/18/05
- Next message: John Blair: "Re: Cannot connect remotely to MSDE2000 database"
- Previous message: Jeter: "Install problem"
- In reply to: Andrea Montanari: "Re: Semnt.dll version after new instance installed"
- Next in thread: Andrea Montanari: "Re: Semnt.dll version after new instance installed"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 18 Feb 2005 17:21:10 +0200
OK Andrea,
Got it... I have already found about upgrading a specific instance...
I have also downloaded your DbaMgr, very nice and usefull application!
Thank you very much.
Arhontis
"Andrea Montanari" <andrea.sqlDMO@virgilio.it> wrote in message
news:37mcq1F5eu801U1@individual.net...
> hi Arhontis,
> Arhontis wrote:
> > Hello Andrea,
> >
> > Thanks for the reply, I will proceed on upgrading the second instance
> > of the MSDE to SP3, but not just now.
>
> please do it ASAP
>
> > Do you have any info about the SEMNT.DLL version conflict in the
> > common 80\Binn directory?
> >
> > Should I delete the newly create files (older) and rename back the
> > (newer version) files?
>
> as these components are shared among all instance, I'd stick with the new
> ones, so that both the retail version and the sp3 version can take
advantage
> of them.... just a caveat... as you in your initial post talked about SQL
> Server and not MSDE being already installed at 8.0.194 build, I do not
know
> if some client tool from the origianal SQL Server installation, MSDE sp3
> does not install/upgrade, still requires the origianal version...
> I'd copy them in a temp folder and try running both instances with the
newer
> dlls, to see if something brokes, before deleting them...
>
> > And something last, how can I upgrade the secont instance (older
> > version) that I have installed to the SP3?
>
> if the "older" instance is a SQL Server instance, you have to run the full
> sp3 package, where you can eventually identify and set the instance name
(in
> case of a named instance)...
> if the "older" instance is a MSDE instance, you have to update it via the
> upgrade you can download at
> http://www.microsoft.com/sql/downloads/2000/sp3.asp, using the
> sql2kdesksp3.exe package...
> you have to provide the
> INSTANCENAME="name"
> parameter to upgrade a named instance, where this parameter is not
required
> for a default instance...
> so the minimal command line will be:
> c:\...\>setup.exe /upgradesp SQLRUN UPGRADEUSER=sa
> UPGRADEPWD="SAstrong_password" /L*v "c:\MsdeLog.txt"
> add INSTANCENAME="name" for a named instance
> add SECURITYMODE=SQL for mixed mode authentication
> add DISABLENETWORKPROTOCOLS=0 to enable network protocols
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> --------- remove DMO to reply
>
>
- Next message: John Blair: "Re: Cannot connect remotely to MSDE2000 database"
- Previous message: Jeter: "Install problem"
- In reply to: Andrea Montanari: "Re: Semnt.dll version after new instance installed"
- Next in thread: Andrea Montanari: "Re: Semnt.dll version after new instance installed"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
