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 8 and MSDE 2000

Hello,
I have MSDE 8 installed on my Win2k server as it is is required by Veritas
Backup Exec.I would also likw to use this server for WSUS, which requires
MSDE 2000. Can these co-exist on the same server?
Thanks
hi,
mpapier wrote:
> Hello,
> I have MSDE 8 installed on my Win2k server as it is is required by
> Veritas Backup Exec.I would also likw to use this server for WSUS,
> which requires MSDE 2000. Can these co-exist on the same server?
>
actually MSDE 8 should be MSDE 2000, as no MSDE 8 is available, but 8.0 is
the internal version of the current SQL Server product...
MSDE (1.0) is based on SQL Server 7.0, where MSDE 2000 is based on SQL
Server 2000
another MSDE version, WMSDE has been made available for SharePoint, based on
MSDE 2000 with some restrictions on database size left out, as SharePoint
could need a database size beyond the actual 2gb limit of traditional
MSDE...
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
|||So, you are saying I already MSDE 2000?
When I try to install WSUS it stops to tell me I do not have the proper
database software installed.
"Andrea Montanari" wrote:

> hi,
> mpapier wrote:
> actually MSDE 8 should be MSDE 2000, as no MSDE 8 is available, but 8.0 is
> the internal version of the current SQL Server product...
> MSDE (1.0) is based on SQL Server 7.0, where MSDE 2000 is based on SQL
> Server 2000
> another MSDE version, WMSDE has been made available for SharePoint, based on
> MSDE 2000 with some restrictions on database size left out, as SharePoint
> could need a database size beyond the actual 2gb limit of traditional
> MSDE...
> --
> 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
>
>
|||hi,
mpapier wrote:
> So, you are saying I already MSDE 2000?
> When I try to install WSUS it stops to tell me I do not have the
> proper database software installed.
I think you have WMSDE installed... based on MSDE 2000, but "branded" to
allow more then 2gb of data per data file...
AFAIK still there's no sp4 for that piece of software, but you could ask in
SharePoint or Win2003 NG...
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

MSDE 2000 behind WSUS server

Hello,
I'm a network / server guy at heart who has been given a quasi-DBA hat
to wear lately, so bear with me.
I have a WSUS (localized Windows updates) server that uses MSDE 2000
as its back end. Since last weekend I started to get an error that
points to a database problem. For the curious, read this:
http://support.microsoft.com/kb/910847
I am disgusted that I cannot go somewhere to download the hotfix, but
rather, I have to call and ask for it. And hope to not get charged for
the call. So, what I'm looking for are utilities that will allow me to
peek inside the database and try to do some cleanup. I'm not finding
much.
I found some command line utilities buried in the directory structure,
like the query tool osql.exe, and dtsrun.exe for DTS packages. But
anything this low level quickly puts me out of my comfort zone. It
seems as though Microsoft has gone to great lengths to keep the
innards of WSUS a secret. Anybody have any ideas how to expose them?
Thanks,
Justin
what.. you want to know more about the schema?
I don't think that it's reccomended that anyone go into the schema and
change anything.. if that's what you're referring to
I know in a heartbeat a real SQL person can dig through a 100 tables in an
hour and have a clue whats going on
<jschick@.aafp.org> wrote in message
news:1177614911.411800.103200@.r3g2000prh.googlegro ups.com...
> Hello,
> I'm a network / server guy at heart who has been given a quasi-DBA hat
> to wear lately, so bear with me.
> I have a WSUS (localized Windows updates) server that uses MSDE 2000
> as its back end. Since last weekend I started to get an error that
> points to a database problem. For the curious, read this:
> http://support.microsoft.com/kb/910847
> I am disgusted that I cannot go somewhere to download the hotfix, but
> rather, I have to call and ask for it. And hope to not get charged for
> the call. So, what I'm looking for are utilities that will allow me to
> peek inside the database and try to do some cleanup. I'm not finding
> much.
> I found some command line utilities buried in the directory structure,
> like the query tool osql.exe, and dtsrun.exe for DTS packages. But
> anything this low level quickly puts me out of my comfort zone. It
> seems as though Microsoft has gone to great lengths to keep the
> innards of WSUS a secret. Anybody have any ideas how to expose them?
> Thanks,
> Justin
>

MSDE + SSL

Hi!
I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003 OWA.
I installed SP1 for Win2003, WSUS and I created a certificate for OWA with
help from SelfSSL.
After this, I cant start my Backup Exec services, complaining about some SSL
error:
SSL Security error
ConnectionOpen (SECDoHandshake()).
and
[DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
I think all this is a problem with SSL and MSDE.
Veritas says "talk to Microsoft" and gues what MS says...
What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE (8.0)
run nice beside SSL for our OWA access.
Thanks!
Mattias
hi Mattias,
MrM wrote:
> Hi!
> I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003
> OWA. I installed SP1 for Win2003, WSUS and I created a certificate
> for OWA with help from SelfSSL.
> After this, I cant start my Backup Exec services, complaining about
> some SSL error:
> --
> SSL Security error
> ConnectionOpen (SECDoHandshake()).
> and
> [DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
> --
> I think all this is a problem with SSL and MSDE.
> Veritas says "talk to Microsoft" and gues what MS says...
> What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE
> (8.0) run nice beside SSL for our OWA access.
>
please try having a look at
http://support.microsoft.com/default.aspx?id=309398 and
http://www.fftf.org/news/Aug05feed/M...ouble.rss.html
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