Microsoft SQL Server
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
 
User Name:
Password:
Remember me
 
Go Back   Dev Articles Community ForumsDatabasesMicrosoft SQL Server

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Display Modes
 
Unread Dev Articles Community Forums Sponsor:
  #1  
Old March 27th, 2007, 11:18 AM
nad23 nad23 is offline
Registered User
Dev Articles Newbie (0 - 499 posts)
 
Join Date: Mar 2007
Posts: 1 nad23 User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 3 m 54 sec
Reputation Power: 0
Licensing and DB capacity

hello,
i dnt know if this is the right place, i'm sorry for that.
Well, I just i got a proposal from a company to develop a software for database management. I have some doubts about licensing the back-end database. My doubts are:

1. If I'm using Sql Server as the backend and the .sql file placed on the server where this .sql file will be accessed by about 20 clients, will the customer (company) have to purchase a license for the sql server? If yes, how this can be done? Does the company have to purchase a license for each client and server for accessing contents of the .sql file? Actually, there will be only 1 server and abt 20 clients.


2. Does the developer need to purchase a seperate license for distributing the .sql file?

3. Also, wat is the maximum capacity of an sql database size? I'm asking this because as per my requirements, the company will be using the database at a rate of 1GB per month. So, by end of a year, it will be 12 GB.


NOTE: No Sql Server Software will be installed on client machines.

In brief, my doubt is: Do we need license for reading and writting to .sql file contents and do we need seperate license for distributing them?

Please, somebody can help me for the licensing information and also for the database size? the database will be also used for remote access.

Thank you.

Reply With Quote
  #2  
Old September 6th, 2007, 09:00 PM
namtaru2007 namtaru2007 is offline
Registered User
Dev Articles Newbie (0 - 499 posts)
 
Join Date: Sep 2007
Posts: 1 namtaru2007 User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 2 m 42 sec
Reputation Power: 0
DB capacity is regulated by how big your disc (s) are, thats all, so if you need more Db room, just buy more discs to be basic about it. There is no space limitation that you are going to need to worry about on the software side. You can even spread the file system across several discs if you need to.

Licensing, Well as far as MSSQL2k its per connection or Per Proc. Typically you want to license your MS SQL product as Per proc as per connection can get costly, im not sure on MSSQL 2005 as I havent looked at the licensing on that yet.

You can freely move your database around all you want but if you are going to open it up you will need a licensed SQL server, as I get it the server is what is licensed not the DB itself. but what good is one with the other right?

If anyone can correct me, feel free but im pretty sure my information is accurate here.

Also, Front ends ( like clients, web apps whatever) wont need licensing to send Queries the SQL server.

Reply With Quote
Reply

Viewing: Dev Articles Community ForumsDatabasesMicrosoft SQL Server > Licensing and DB capacity


Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump


Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 





© 2003-2008 by Developer Shed. All rights reserved. DS Cluster 5 hosted by Hostway
Stay green...Green IT