Printable View
b'cos of cost of ms sql server s/w, we are developing a network application (server and clients), the clients will access the ms sql database on the server system. ms sql server 2000 will be installed on the server system, plz what is the minimum ms sql installation requirement for the clients to request for data from the server.
oyad
thanx guys
To fetch data only? What kind of front-end will you use? I believe ADO is all you need...
The clients do not need sql server installed on their systems, only on the server. Dee-u is right, ADO or other data access component is all thats required to retrieve, insert, and update data. There is a licensing issue though. SQL Server, depending on the number of licenses your company purchased, can only have a certain number of concurrent connections.
Quote:
Originally Posted by RobDog888
plz, i don't get this licenses stuff u're talking about, including number of concurrent users depending on it :confused:
When you purchase SQL Server you can purchase licenses for each connection your going to have to the SQL server, like an applications single connection, but if your app uses allot of users and they all connect to the server at the same time then those are all concurrent connections. Think of it like sharing. If they both use the db at the same time vs. having to take turns to use the db.
Licenses can be purchased in single license or in packs that usually are cheaper to buy.
I may be out dated RD, but I thought they switched to a processor capacity based licencing senario making the number of connections are irellevant.
-tg
No, they added that as another licensing option. You can get SQL Server by connections or by processors. I remember reading a thread a while ago where szlamany posted the link from MS where it shows something to this effect. :)
Hmmmm, didn't realize they kept the old-style.... good to know for future reference.
-tg
Yes, they actually have three licensing schemes. I think its still called "Per Seat", "Per Server", and "Per Processor", but dont quote me on the exact names as I cant remember exactly. :blush: I hope its not old age. :eek: :( :lol:
Of course if you do have a licence that limits concurrent connections then careful handling of your recordsets and connection objects can make a significant difference to the number of users who can actually use the system concurrently. For instance if your application keeps a connection to the server open throughout use then you can only have as many instances of it running as you have client licences. However if the programme only holds open a connection for say 5% of the time then you could usually have 10 or more times as many instances of the programme running happily together.