MSDE - Multiple versions coexist?

While setting up for HP Insight Manager...
Microsoft provided documentation is leading me to believe that MSDE 2000 SP3
and previous versions of MSDE could coexist on one box.
Is that true?
I installed MSDE 2000 SP3 on one of my servers which had a previous MSDE
version with existing active databases. The result was that though databases
were still running, I had difficulty seeing the certain databases through
Enterprise Manager.
hi,
"mahlerdw" <mahlerdw@.hotdeleteme.com> ha scritto nel messaggio
news:O7wPFHaoEHA.2032@.TK2MSFTNGP10.phx.gbl
> While setting up for HP Insight Manager...
> Microsoft provided documentation is leading me to believe that MSDE
> 2000 SP3 and previous versions of MSDE could coexist on one box.
> Is that true?
> I installed MSDE 2000 SP3 on one of my servers which had a previous
> MSDE version with existing active databases. The result was that
> though databases were still running, I had difficulty seeing the
> certain databases through Enterprise Manager.
yese , up to 16 instances of SQL Server 2000 and MSDE 2000 at different
service pack level can coexist on the same box.
1 instance will be the default instance, locally available as "(local)" or
generally available as "ComputerName", while all other instances will be
named instances, reachable with teir complete name, made up by the computer
name and instance name, in the form "ComputerName\InstanceName"
what kind of problem are you facing?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I have a server running MSDE and two existing databases or instances. I am
uncertain of the version or how to determine the version.
I'm installing HP Insight manager, which requires MSDE 2000, SP3. I
installed MSDE 2000, SP3 and created the new instance for Insight Manager.
The application worked and the existing databases/instances were accessible
and continued to work.
A few days later, an Programmer/Administrator was trying to
monitor/manipulate one of the previously existing databases via Enterprise
Manager and noticed he could not see it the applications utilizing the
databases worked fine.
I uninstalled the MSDE 2003. The Programmer/Administrator then was able to
monitor/manipulate the previously existing databases via Enterprise Manager.
I'm not certain my explanation is clear. Any help you can provide is
appreciated.
DWM
[vbcol=seagreen]
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rgrn3F1ad8ggU1@.uni-berlin.de...
> hi,
> what kind of problem are you facing?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
|||hi,
"mahlerdw" <mahlerdw@.hotdeleteme.com> ha scritto nel messaggio
news:%23$d0IXkoEHA.3464@.tk2msftngp13.phx.gbl
> I have a server running MSDE and two existing databases or instances.
> I am uncertain of the version or how to determine the version.
> I'm installing HP Insight manager, which requires MSDE 2000, SP3. I
> installed MSDE 2000, SP3 and created the new instance for Insight
> Manager. The application worked and the existing databases/instances
> were accessible and continued to work.
> A few days later, an Programmer/Administrator was trying to
> monitor/manipulate one of the previously existing databases via
> Enterprise Manager and noticed he could not see it the applications
> utilizing the databases worked fine.
> I uninstalled the MSDE 2003. The Programmer/Administrator then was
> able to monitor/manipulate the previously existing databases via
> Enterprise Manager.
> I'm not certain my explanation is clear. Any help you can provide is
> appreciated.
actually there's no reason for that... all instances can be running
(resources allowing it) with no consequences...
each instace will have it's onw TCP address , provided by the service
listening on UDP 1434 port..
check the services (SQL Server services) are running and address each
instance with it's correct name (full name for named instance)
I do not know HP Insight manager, so I'm not able to provide fupport for
that tool/application
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply