[RESOLVED] Difference between standalone and client server based application

Difference between standalone and client server based application

--------------------------------------------------------------------------------

Hi all,
I have developed database applicaiton using VB6.0 and Access. Now im developing the same application with VB6.0 and SQL Server2000.

SQL server will be running in one machine and the users will be accessing the database using the application i developed. my question is when I develop do I have to special consideration on the application?. but at the moment im developing it in my standalone pc. if I install the same application in multiple computers what are the things I have to consider. Please let me know how simply I can understand this concept.

Thanks
MRiz

It may be better to keep MsAccess in the loop by "linking" tables to SQL server tables, and keeping the client programs talking to access tables (which will be linked ODBC tables).

rizanmsm:

I think the first thing you are going to have to consider is the cost.

I may be wrong, but it is my understanding that the desk top version of SQL Server 2000 will not work in a "true network" situation, so you will have to purchase SQL Server which will be rather expensive. You would have to check Microsoft's Web site to find out the exact price.

This is the main reason you see a lot of people using MySQL. MySQL is free.

Good Luck

MsAccess may also give you the ability to link tables to MySQL (via ODBC), I think.

AIS4U or anyone can help me,
Im having a SQL2000 which didnt ask any cd key got it from a friend from US. so you think if I install the client connectivity drivers in client computers and install my software will it work? this is the first time im developing a applicaiton for a network environment but it will be less than 5 users using my application.

What about writing program to MYSQL is it similar than that of SQL2000? if you have any small sample applicaiton which connect to MySQL with VB6.0 (include add, update, delete accessing to records etc.. could you be able to send?)

Thanks
Rizan

MS SQL SERVER has many editions available.

EXPRESS - installs on a non-server PC and is network accessible. This was called MSDE with MS SQL 2000 - now with MS SQL 2005 it's called EXPRESS.

This version is free

so how do i find my version of SQL Server2000 and findout whether it supports in a networked environment?

Quote:

---

Originally Posted by rizanmsm

so how do i find my version of SQL Server2000 and findout whether it supports in a networked environment?

---

They all are.

so dat means i dont have to worry about insalling my applicaiton wich i develop with vb6.0 and the SQL 2000. it will support in the network envoronment isnt it? but pls read the AIS4U's reply dat made me confused.
thanks

MSDE (the free SQL Server) is limited to 5 concurrent users, for one thing, IIRC. It's definitely not an industrial strength database.

It will be a step up from the Jet Engine.

5 concurrent users is not really true...

Quote:

---

When there are more than eight active operations at the same time in the same instance of the database engine, the governor implements a slight wait before each logical read or write to a data file

---

From http://msdn.microsoft.com/library/de...r_sa2_0ciq.asp

Quote:

---

Originally Posted by rizanmsm

so dat means i dont have to worry about insalling my applicaiton wich i develop with vb6.0 and the SQL 2000. it will support in the network envoronment isnt it? but pls read the AIS4U's reply dat made me confused.
thanks

---

If you want to code for MS SQL 2000 do it - the MSDE version is free and powerful - after that you have other paid versions available.

How many actual users do you have?

mySql cannot compare to MS SQL Server...

Here's a good whitepaper...

http://msdn.microsoft.com/library/de...sderoadmap.asp

and another good short article...

http://msdn.microsoft.com/library/de...ar_ts_8ynn.asp

and a comparison chart of features...

http://msdn.microsoft.com/library/de...ar_ts_8ynn.asp

Quote:

---

Originally Posted by szlamany

If you want to code for MS SQL 2000 do it - the MSDE version is free and powerful - after that you have other paid versions available. mySql cannot compare to MS SQL Server...

---

I can confirm this statement. I wrote a benchmark that all it did was dump INSERT INTO's as fast as possible into MSDE, MySQL, and MSSQL. MSDE and MSSQL were nearly identical. MySQL had between 5 and 20 times longer delays between successive INSERTs.

i will be having less than 10 users. U think it will support?

@davesell - The nice thing about MSDE is that it the same database engine (SQLSERVER.EXE) as every other version of MS SQL server. That's really incredible for a free product. Having some features intentionally turned off is a reasonable thing for MS to do...

Having 8 concurrent transactions cause a speed delay is a reasonable way for MS to make sure this free product is not abused. You can have 100 people connected to it just like any other version of MS SQL server - as long as the activity level is low.

@everyone - MS SQL Server 2005 - Express edition - is also free - replaces MSDE - and doesn't have the same 8 concurrent transaction governor. I can't wait till all my customers go with 2005 - the new features are great!

Ok - that's enough of a MS SQL rant for me today ;)

Quote:

---

Originally Posted by rizanmsm

i will be having less than 10 users. U think it will support?

---

That's exactly the level of users that MS had in mind with MSDE (as long as they are not all running transaction intensive operations!).

thanks everyone
tc

One more MSSQL rant.

Quote:

---

i will be having less than 10 users. U think it will support?

---

The number of Users/connections does not matter. All SQL Server versions support 32,767 connections. As already "ranted by szlamany", the imposed limit is on "currently executing batches". If there are 5 batches (user batches only, does not include system batches) being performed the 6th is purposely slowed down. So instead of taking 50ms it might take 100ms, hardly noticeable by users. The number of concurrent batches determines the slow down. This is no longer true in SQL Express 2005.

Quote:

---

It's definitely not an industrial strength database.

---

Depends on your definition of industrial strength. I ran a website that used MSDE, not a lot of traffic maybe 2000-3000 hits/day but every page had to execute at least 3 stored procedures all of which queried, updated and inserted data on every call.

I periodiclly executed the DBCC CONCURRENCYVIOLATION which showed that never was there more than 8 batches executing at once. And the number of times 6 batches were executing at once was less than 20, in two years.