Re: SQL Server and MSDE

From: Norman Yuan (nobody_at_nowhere.no)
Date: 12/02/04 

Date: Thu, 2 Dec 2004 07:56:15 -0700

SQL Server and MSED is the same thing, except MSED does not come with visual
management tool (Enterprise Manager) and a few limitations on its
functionalities.

So, to you question:

1. No, MSDE does not get installed when you install full SQL Server. If the
SQL Server on your computer is for development, there is not need to put
MSDE, unless you want to learn how to integrate your app with MSDE (for
example, learn how to use command line to manage SQL Server/MSDE, as oppose
to Enterprise Manager).

2. MSDE allows up to 8 concurrent access (3 used by itself?), meaning there
is no difference from full SQL Server when less then 8 concurrent access.
When more accesses reach the MSDE, it will slow down the process greatly (to
encourage you switch to full SQL Server!). Note, it is concurrent access
count, not number of users who use the MSDE database application. With well
designed data access approach, MSDE could easily cope with 20, 50 or even
more users. All depends on how the data is accessed. I have being using MSDE
in a 25-use office with quite heavy data access since MSDE1.0 (SQL Server 7)
and never hit the MSDE "Slow down" point.

3. Almost everything in database you designed on SQL Server can be used
directly on MSDE, except something that does not come with MSDE, like
English Query, Reporting Services. You can design a database in either SQL
Server, or MSDE, including tables, Views, Stored Procedures and detach the
database from one and attched to the other wothout any change.

"Marathoner" <Marathoner@discussions.microsoft.com> wrote in message
news:B137F085-969E-4659-BD9C-73693CC992D0@microsoft.com...
> I need someone to clear up a few questions I have about MSDE. I have SQL
> Server 2000 installed on my machine. Does this mean I also have MSDE
> installed or is this a separate installation?
>
> Can you install MSDE on a sever to be accessed by 5 users running a
WinForm
> application from their machines?
>
> Lastly, can I create stored procs in SQL Server 2000 and incorporate them
in
> an instance of MSDE running on another machine?
>
> Thanks in advance,
>
> Robert
> --
>
>

Relevant Pages

  • Re: MSDE licensing rules
    ... > The only problem I ran into was when to setup MSDE. ... > approach is to only install it, with an instancename, when there is no ... Andrea Montanari (Microsoft MVP - SQL Server) ...
    (microsoft.public.sqlserver.msde)
  • Re: Administering MSDE with Enterprise Manager
    ... SETUP SAPWD="wombat" created 'Windows Only Authentication'. ... the MSDE machine from those on the machine that I was connecting from. ... > A. You can only use SQL Server tools and services in conjunction ... >> created during MSDE's install. ...
    (microsoft.public.sqlserver.connect)
  • Re: Administering MSDE with Enterprise Manager
    ... SETUP SAPWD="wombat" created 'Windows Only Authentication'. ... the MSDE machine from those on the machine that I was connecting from. ... > A. You can only use SQL Server tools and services in conjunction ... >> created during MSDE's install. ...
    (microsoft.public.sqlserver.msde)
  • Re: Administering MSDE with Enterprise Manager
    ... SETUP SAPWD="wombat" created 'Windows Only Authentication'. ... the MSDE machine from those on the machine that I was connecting from. ... > A. You can only use SQL Server tools and services in conjunction ... >> created during MSDE's install. ...
    (microsoft.public.sqlserver.setup)
  • Re: Named Instance, Connectivity Question
    ... with SQL Server 2000 Client ... I installed MSDE 2000 under Named Instance. ... yes, you can install only a named instance, only a default instance, or upt ...
    (microsoft.public.sqlserver.msde)