1. Here is the link
http://msdn.microsoft.com/library/?u...asp?frame=true
Read the paragraph
"Like all versions of SQL Server 2000, SQL Server 2000 Personal Edition and
MSDE 2000 allow 32,767 connections to an instance of the database engine.
There is no limit for the number of connections that can be executing
operations at the same time."
There is no limit on connections. 25 concurrent users you probably met in
documentation is a reasonable number Microsoft suggest you aim for. They
just simply telling you that if you have more than 25 concurrent users,
simultaneously running quires on your website, it's time to upgrade to real
SQL since users will get a slow response. Since 20 of them will be on hold.
2. There are no tools like "Enterprise Manager". They just do not come with
it inside of that download you downloaded from Microsoft site. But if you
have it installed already because you have real MS SQL somewhere else then
they are going to work perfectly.
The same goes to Book online. Just use it online. I would not call it a
limitation of MSDE.
3. What exactly do you mean by "MSDE is a file based database like MS
Access". I am affraid you are confusing terms here.
Let me give you an example of "file based database like MS Access"
Let say you have MS Access database on one machine. And 10 others are trying
to write to it.
Every machine will have to open the remote file, read necessary info, scan
indexes using File IO,....
And everything done through the network. Just to get one record Access
should issue hundreds disk IOs to scan the index. Over the network it's a
killing.
So "file based database" is the database that using Disk IO commands. And as
a consequence it's very inefficient. There is no coordination in those IOs.
As opposite MSDE works exactly the same as MS SQL. It receives SQL commands
over the network then does local disk IOs and returns you only that one
record.
This is called SQL database. (Not MS SQL, Oracle is SQL database too.)
It's much more efficient since there is a coordination between disk IOs.
Caching is possible.
So the bottom line is MSDE is a perfect database for not heavy trafficking
web sites. Yes, it does eat more resources than MS Access but it's a good
price to pay for benefits.
George.
"Peter O'Reilly" <Peter_OReilly@timeinc.com!N!O!.S!P!AM!> wrote in message
news:u4Kn1lGLEHA.2400@tk2msftngp13.phx.gbl...[color=blue]
> "George Ter-Saakov" <nospam@hotmail.com> wrote in message
> news:elSDFW9KEHA.3944@tk2msftngp13.phx.gbl...[color=green]
> > A correction.
> > MSDE is exactly the same server as MS SQL server excluding some rarely[/color]
> used[color=green]
> > features (replication, ...).
> >[/color]
>
> Sorry, not so. It is a tool "built and based on core SQL Server
> technology". It's purpose is to provide "a seamless upgrade path from[/color]
MSDE[color=blue]
> 2000 to SQL Server if an application grows beyond the storage and
> scalability limits of MSDE 2000."
> (
http://www.microsoft.com/sql/msde/pr...o/overview.asp) Try[/color]
installing[color=blue]
> SQL Server on Windows 98 desktop - you can't, but you can for MSDE.[/color]
There's[color=blue]
> a good reason for this.
>[color=green]
> > 1. Does not have connection limit. (Reasonable)[/color]
>
> It does have a connection limit of 25 connections.
>
>[color=green]
> > 2. It does have artificial limit = 5 of the amount of queries executed[/color][/color]
at[color=blue][color=green]
> > the same time. But the next (after 5) query is not rejected but is put[/color][/color]
on[color=blue][color=green]
> > hold. And considering that queries are running within milliseconds it's[/color]
> not[color=green]
> > an issue with not heavy trafficked website.
> >[/color]
>
> Other limitations of MSDE versus SQL Server:
> a.. No Enterprise Manager
>
> b.. No Query Analyzer
>
> c.. No Index Tuning Wizard
>
> d.. Only 2GB RAM
>
> e.. Only 2GB database size limit
>
> f.. Only 2 CPUs
>
> g.. Only five concurrent batch workloads or 25 concurrent connections[/color]
for[color=blue]
> websites
>
> h.. No Database Server Failover Support
>
> i.. No Full-text search
>
> j.. No SQL Server Profiler
>
> k.. No Import and Export Wizards
>
> l.. No OLAP
>
> m.. No English Query
>
> n.. No SQL Books Online
>
> o.. No Full or Bulk-Logged recovery model support (only simple)
>
> (
http://www.teratrax.com/articles/msd...ql_server.html)
>
> The bottom line is MSDE is a file based database like MS Access (Jet) and
> its limitations are due to the Windows file system which is not optimized[/color]
in[color=blue]
> this regard. (That's why there's a true OLAP database like SQL Server).
> The plus to MSDE is that your application may migrate a _little_ bit[/color]
easier[color=blue]
> to SQL Server. The downside is Jet is much less of a resource hog, (e.g.
> memory for sure and disk space depending on your setup) than MSDE. Most
> importantly, Load testing I have found Jet to be able to handle 10
> concurrent write operations and only 5 for MSDE.
>
> From my personal experience using both, I'd stick with your existing
> Access/Jet application. MSDE is not an "upgrade" option.
> --
> Peter O'Reilly
>
>[/color]
