Upsizing mdb to MSDE

[hooi]

Hi,

I've three questions:
1. I'd like to know how to go about upsizing mdb be to MSDE. Should I use the same Upsizing Tool for this purpose?
2. How is security taken care of when data is upsized to MSDE. I presume the FE will continue to use the mdw file, how about the MSDE?
3. Has anyone tried to allow users to access the database via the web using Visual Basic.Net, is there anything I should be aware of especially user login authentication (and possibly security issue)?

Thanks...

 

[hooi]

Hi Pat,

Thank you for your reply.

Does the 4 users being referred to accessing the database concurrently?
Will it be slower than the full-fledge papa-SQL Server?
Will it be as slow with the SQL Server if the number of concurrent user is 4?

Thanks...

 

[hooi]

Hi,

I've found the answers in the link below:
http://www.microsoft.com/sql/msde/techinfo/workloadgov.asp

The slow performance is caused by workload governor

 

[hooi]

Thank you Pat for your insight.

 

[Kodo]

The MSDE has more than 4 allowable connections.

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. The only effect of the workload governor is that it starts slowing down the database engine when more than eight operations are actively running at the same time.

and remember, some of that is based on how you code your application.

 

[Kodo]

The source I quote was direct from the MS document about how it governs.
You can use things like SQLExecMS to admin an MSDE. The MSDE is very useful for controlled environments (intranets) where budgets are tight and you need more than an access db.

 

[Kodo]

here's the MICROSOFT document on the governor in which I quoted my text.

http://download.microsoft.com/download/b/3/6/b36add63-894c-4c64-a49b-6e8696932d7b/WorkLoadGov.doc