MSDE along side WMSDE?

I've got a situation where WSUS is already installed on a server and I'm
looking
at moving my anti-virus system on to the same server, however my AV uses
MSDE. The server is running 2003 and therefore WSUS is running in WMSDE.
I take it I can't use WMSDE for my AV solution so I'd like to know, is it
viable to simply install MSDE 2000 along side WMSDE, or will I have to move
WSUS out of WMSDE and into MSDE 2000?
I assume I'll have some conflicts at minimum with the ports clashing if the
two live together, and there are likely to be other major problems.
Does anyone have any ideas or suggestions?
hi,
AC wrote:
> I've got a situation where WSUS is already installed on a server and
> I'm looking
> at moving my anti-virus system on to the same server, however my AV
> uses MSDE. The server is running 2003 and therefore WSUS is running
> in WMSDE.
> I take it I can't use WMSDE for my AV solution so I'd like to know,
> is it viable to simply install MSDE 2000 along side WMSDE, or will I
> have to move WSUS out of WMSDE and into MSDE 2000?
> I assume I'll have some conflicts at minimum with the ports clashing
> if the two live together, and there are likely to be other major
> problems.
> Does anyone have any ideas or suggestions?
WMSDE should not be used for other means then the ones it has been released
for, so just install another instance of MSDE for your AV...
you'll have no "ports clashing" or conflicts, as SQL Server 2000 allows up
to 16 instances to be locally installed...
only one of them can be the "default" instance, litening (by default) on
TCP/IP 1433 where all other instances have to be named instances, where
their full name is composed by the ComputerName\InstanceName...
you can leave for all of them the default "dynamically assigned port"
setting, an additional service, the SQL Server Resolution Service is then
listening on UDP 1434 to resolve and address the correct named instance on
it's appropriate port..
if you manually set the TCP/IP port the named instance(s) will be listen on,
you can close (on your firewall) the UDP 1434 port as it is no longer
needed, but you'll probably need to specify an ALIAS (via Client Network
Utility, cliconfg.exe) on all your remote clients..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you very much for your reply Andrea.
Although I've seen installations with several MSDE instances before I never
thought about how they worked untill now, therefore I've never even realised
there is a manager service to resolve the ports for each service!
Thank you for enlightening to this!
"Andrea Montanari" wrote:

> hi,
> AC wrote:
> WMSDE should not be used for other means then the ones it has been released
> for, so just install another instance of MSDE for your AV...
> you'll have no "ports clashing" or conflicts, as SQL Server 2000 allows up
> to 16 instances to be locally installed...
> only one of them can be the "default" instance, litening (by default) on
> TCP/IP 1433 where all other instances have to be named instances, where
> their full name is composed by the ComputerName\InstanceName...
> you can leave for all of them the default "dynamically assigned port"
> setting, an additional service, the SQL Server Resolution Service is then
> listening on UDP 1434 to resolve and address the correct named instance on
> it's appropriate port..
> if you manually set the TCP/IP port the named instance(s) will be listen on,
> you can close (on your firewall) the UDP 1434 port as it is no longer
> needed, but you'll probably need to specify an ALIAS (via Client Network
> Utility, cliconfg.exe) on all your remote clients..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
sql

MSDE & WMSDE

What is the diffrence between MSDE 2000 and WMSDE? I have two applications
that require these databases and I am concerned there might be issues in
using them on the same server:
SmarterTicket / MSDE 2000
Windows SharePoint Services / WMSDE
Thanks - Jody
hi Jody,
Jody wrote:
> What is the diffrence between MSDE 2000 and WMSDE? I have two
> applications that require these databases and I am concerned there
> might be issues in using them on the same server:
> SmarterTicket / MSDE 2000
> Windows SharePoint Services / WMSDE
> Thanks - Jody
WMSDE is a customized version of MSDE 2000 distributed along with and only
available with SharePoint...
it has been modified to fit SharePoint needs and you should avoid using it
for your own databases..
I do not have a WMSDE eula available, but I think it prohibits a shared use
with other apps and related databases..
install 2 separated instances, 1 of WMSDE to be used by SharePoint and
another MSDE one to be used by your other apps.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://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
|||Andrea,
In reference to you comment:
"...it has been modified to fit SharePoint needs and you should avoid using
it for your own databases..."
Do you mean that I should avoid using WMSDE with WSS or along side of
SmarterTicket becasue it uses MSDE?
Thanks - Jody

> hi Jody,
> Jody wrote:
> WMSDE is a customized version of MSDE 2000 distributed along with and only
> available with SharePoint...
> it has been modified to fit SharePoint needs and you should avoid using it
> for your own databases..
> I do not have a WMSDE eula available, but I think it prohibits a shared use
> with other apps and related databases..
> install 2 separated instances, 1 of WMSDE to be used by SharePoint and
> another MSDE one to be used by your other apps.
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://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
>
>
|||hi Jody,
Jody wrote:
> Andrea,
> In reference to you comment:
> "...it has been modified to fit SharePoint needs and you should avoid
> using it for your own databases..."
> Do you mean that I should avoid using WMSDE with WSS or along side of
> SmarterTicket becasue it uses MSDE?
I mean WMSDE should be used only by SharePoint and let SmarterTicket uses
another MSDE instance ..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://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

MSDE & WMSDE

Hi all,
i'm very new on MSSQL, recently i need to setup Windows
SharePoint Services and came across about the MSDE.
Appreciate if someone can answer my question below.
1) What is the different between MSDE & WMSDE ?
2) Possible description on the following executable
files? Or website.
bcp.exe, cnfgsvr.exe, dcomscm.exe, osql.exe,
sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and
svrnetcn.exe
3) What is storage limit? MSDE have limitation on 2Gb of
storage limit, how about WMSDE?1) What is the different between MSDE & WMSDE ?
WMSDE is a special MSDE on steroids without the 5 user limit and
without the 2GB limit
but you can't search in sharepoint sites
Re 2gb limit:
for most installations you shouldn't wory about this ceiling
you should worry about emphasizing to users that Sharepoint sites are
not for dumping anything like they did with their network shares
for others i recommend msd2d.com
it is a great place for the beautiful Sharepoint technlogies
hope this answered some of your questions
PS: i found a title from Elsevier very helpful..check amazon
the authors are from HP
mawrid
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message248322.html