Question: How are SQL-Server's technologies dependent on the number of users? After all, don't those same technologies have value for 1 user as well as 1000. The point is that SQL-Server's abilities transcend the number of users/quantity of data. Elements like stored procs, transaction logging, etc. have value regardless of the number of users.

As far as deploying MSDE outside the context of the standard/enterprise version of SQL, I think then it has a limited role. But, they are roles that have advantages over DBF's. Yes, there are also disadvnatages.

FWIW, the point about offline, mobile processing was one that I brought up earlier < g >. The key here is that the engine that manages the offline data is the same as the server engine.

Finally, 80% of the work you do with data should be in a disconnected manner. There are only 4 instances where you need to be connected to the backend data source:

Updates
Deletes
Inserts
Queries

Therefore, if you have 20 or so folks, you may find that at no time, do you have more than 5-8 connections.

And yes, MSDE would make for a great prototyping tool. Then again, if you are prototyping with it, would'nt that mean that your implementation will be SQL-Server? That would make the whole DBF vs. MSDE argument moot.


>I agree that there are cases where MSDE could be usefull. However, the real strength in SQL Server lies with it's technologies which would normally exceed the needs of five concurrent users. Therefore, I still can't see how MSDE can be justified for use beyond a small set of circumstances albeit a good prototyping tool.
>
>I must say that Roxanne's point concerning offline processing with MSDE is the best argument yet for it's use, but only when full-blown SQL Server is already being employed.