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 2ksp3a TO SQL Server 2000, why is upgrade option disabled?

Hi,
I have latest version of MSDE on my win xp machine, I had installed a named version msde using the microsoft bootstrapper along with my application. During installation I had specified the datadir to be something like c:\program files\MyApp\Data
So far so good.
Now I am trying to install SQL Server 2000 dev edition on my computer and was hoping to upgrade this named instance of MSDE, but the upgrade option is disabled. All I can click on is "Create a new instance of SQL Server, or install Client Tools" and "Adv
anced options". Why is that. What am I missing. I read many times that upgrading named instance shouldn't be a problem.
I have to figure this out so that in future my client's can upgrade our MSDE named instance to SQL Server named instance if they need to..
Thanks
dev
correction, I had installed msde using the latest sql2ksp3 exe from microsoft.
thanks
dev
|||You can't upgrade MSDE to Developer Edition, you can only upgrade to SQL
Server 2000 Enterprise Edition or SQL Server 2000 Standard Edition.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:F366A797-A10F-4EAE-8AD7-1BC89ED470C4@.microsoft.com...
> Hi,
> I have latest version of MSDE on my win xp machine, I had installed a
named version msde using the microsoft bootstrapper along with my
application. During installation I had specified the datadir to be
something like c:\program files\MyApp\Data
> So far so good.
> Now I am trying to install SQL Server 2000 dev edition on my computer and
was hoping to upgrade this named instance of MSDE, but the upgrade option is
disabled. All I can click on is "Create a new instance of SQL Server, or
install Client Tools" and "Advanced options". Why is that. What am I
missing. I read many times that upgrading named instance shouldn't be a
problem.
> I have to figure this out so that in future my client's can upgrade our
MSDE named instance to SQL Server named instance if they need to..
> Thanks
> dev
>
|||Jasper thanks for the reply. Where can I find the document which states MSDE can be upgraded to which versions.
Does that mean that my client will have to invest in a server (NT 4.0 Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000 Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
thanks
dev
|||got it, thanks
http://support.microsoft.com/default...b;en-us;823462
|||They'll need a server operating system e.g. Windows 2000 Server or Windows
2003 Standard to install SQL2000 Standard
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:3F461785-F5A1-491F-9A4E-8ED5462409AE@.microsoft.com...
> Jasper thanks for the reply. Where can I find the document which states
MSDE can be upgraded to which versions.
> Does that mean that my client will have to invest in a server (NT 4.0
Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000
Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
> thanks
> dev

MSDE 2ksp3a TO SQL Server 2000, why is upgrade option disabled?

Hi
I have latest version of MSDE on my win xp machine, I had installed a named version msde using the microsoft bootstrapper along with my application. During installation I had specified the datadir to be something like c:\program files\MyApp\Dat
So far so good
Now I am trying to install SQL Server 2000 dev edition on my computer and was hoping to upgrade this named instance of MSDE, but the upgrade option is disabled. All I can click on is "Create a new instance of SQL Server, or install Client Tools" and "Advanced options". Why is that. What am I missing. I read many times that upgrading named instance shouldn't be a problem
I have to figure this out so that in future my client's can upgrade our MSDE named instance to SQL Server named instance if they need to.
Thank
deYou can't upgrade MSDE to Developer Edition, you can only upgrade to SQL
Server 2000 Enterprise Edition or SQL Server 2000 Standard Edition.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:F366A797-A10F-4EAE-8AD7-1BC89ED470C4@.microsoft.com...
> Hi,
> I have latest version of MSDE on my win xp machine, I had installed a
named version msde using the microsoft bootstrapper along with my
application. During installation I had specified the datadir to be
something like c:\program files\MyApp\Data
> So far so good.
> Now I am trying to install SQL Server 2000 dev edition on my computer and
was hoping to upgrade this named instance of MSDE, but the upgrade option is
disabled. All I can click on is "Create a new instance of SQL Server, or
install Client Tools" and "Advanced options". Why is that. What am I
missing. I read many times that upgrading named instance shouldn't be a
problem.
> I have to figure this out so that in future my client's can upgrade our
MSDE named instance to SQL Server named instance if they need to..
> Thanks
> dev
>|||Jasper thanks for the reply. Where can I find the document which states MSDE can be upgraded to which versions.
Does that mean that my client will have to invest in a server (NT 4.0 Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000 Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
thank
dev|||got it, thanks
http://support.microsoft.com/default.aspx?scid=kb;en-us;823462|||They'll need a server operating system e.g. Windows 2000 Server or Windows
2003 Standard to install SQL2000 Standard
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:3F461785-F5A1-491F-9A4E-8ED5462409AE@.microsoft.com...
> Jasper thanks for the reply. Where can I find the document which states
MSDE can be upgraded to which versions.
> Does that mean that my client will have to invest in a server (NT 4.0
Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000
Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
> thanks
> dev

MSDE / SQL Express Question

what is the limitation in terms of connections? I've read something along
the lines of 5-10 connections?MSDE had a 5 concurrent connection 'governor. With SQL Server 2005 Express,
the governor has been removed, and the limit is mostly related to the type
of activity and hardware. Of course, there will be some relationship with
and processor/memory/disk subsystem -up to the limits.
With low to moderate frequency activity (small packets) in a small OLTP
database, you might be able to adequately support 20-30 users. Large
resultsets in a OLAP may only support 1-5 users. Plan to thoroughly test any
implementation.
See specifications at:
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"g" <gregoranton_nospamplease_@.hotmail.com> wrote in message
news:8pIPg.24564$Lb5.16987@.edtnps89...
> what is the limitation in terms of connections? I've read something along
> the lines of 5-10 connections?
>|||On Tue, 19 Sep 2006 02:15:32 GMT, g wrote:
>what is the limitation in terms of connections? I've read something along
>the lines of 5-10 connections?
>
Hi g,
In addition to Arnie's answer: the MSDE workload governor limits
concurrent _WORKLOADS_, not connections. An idle connection is not a
workload, a working connection is. Some connections might even spawn
multiple workloads. So ten, twenty, fifty or even hundred data entry
typists coould all simultaneously be connected to MSDE without ever
hitting the 5-workload limit. But one carefully architected procedure
that spawns multiple connections (not easy to do, but possible) could
bring MSDE to it's knees all by itself.
Oh, and if you surpass the maximum of 5 concurrent workloads, the effect
will be that the workload governor starts to throttle performance. A bit
if you have only 6 workloads, but progressively more as the number of
workloads increases - effectively, MSDE will slow down to an almost halt
if you keep increasing concurrent workloads.
--
Hugo Kornelis, SQL Server MVP