licensing in SQL 2k

MS SQL SERVER

    Sponsored Links

    Next

  • 1. Let me rephrase: Connection Timeouts on local machine ?
    I'm trying to understand the following: a) I've just installed SqlServer Express on two machines -- one my Dev machine to use via VS2005, one on a webserver. b) Just addressing the dev machine to make the scenario simpler: if the sqlservice is running. if the database is local (dif hard drive btw) if the database is attached, and therefore server knows where it is and doesn't have to go and find it, if the db contains only a couple of indexed tables, and the queries are straight forward non-join selects if the tables are indexed, and therefore already basically optimized for queries, why would a connection take 10-15 seconds to make? This is basically 10-15 seconds longer than MySQL and I just don't get it. What is it doing under there that makes it need so much time to get ready to answer a simple SELECT statement? Ie -- what extra features that I will probably never need, can I turn off, so that it is much more responsive? BTW: this happens if it is my own app, or if using SSEE to open a connection to the db -- it just seems to take eons, rather than be instantaneous. I'm hoping here that this has to be a configuration issue (although its the default configuration of the downloadable Express SP-1) because this kind of start up delay is a sales killer in my mind. There is abs no way I could sell an app that takes that much time to 'warm up'. Can anybody help me out with this?
  • 2. Auto truncation of data
    Does anyone know how to configure SQL 2005 to allow auto truncation of data? Tried setting the AUTO ANSI WARNING to False but error message "String or binary data would be truncated" warning appear and data not saved.
  • 3. Registering a New 2000 SQL Server.
    I have a new SQL server but i can't connect to it because it says that i'mnot associated with a trusted SQL server connection. I've tried to change the registration and it keeps giving me the same error. Any suggestions??

licensing in SQL 2k

Postby Ray » Sat, 24 Apr 2004 02:08:29 GMT

What is the difference between client and server licensing?

I have installed with the server / 1cpu option and now 
they tell me I should have picked CAL.  How do I switch?

Thanks,
Ray

RE: licensing in SQL 2k

Postby v-ashrup » Sat, 24 Apr 2004 07:13:08 GMT

Hi Ray,

Below is a Question that I found in the FAQ section of SQL's Licensing.

Q.  How do I license SQL Server 2000? 
   
A.  In general, there are three options for licensing SQL Server in a 
production environment:

Processor license. Requires a single license for each CPU in the operating 
system instance running SQL Server. If you have made a processor 
inaccessible to all operating system copies on which the SQL Server 
software is set up to run, you do not need a software license for that 
processor. This license does not require any device or user client access 
licenses (CALs). 

Server plus device CALs. Requires a license for the device or user running 
SQL Server, as well as a CAL for each client device. 

Server plus user CALs. Requires a license for the computer running SQL 
Server, as well as a CAL for each user.  




Per Processor License - If you buy a per processor license, you DO NOT 
require CALS. It accomodates all the clients that get connected to the SQL 
Server. But, you need to buy a software license for Each of the Processor.

You need to buy Separate CALs for each client that gets connected 
simultaneously to your SQL Server. CALs are available in two options, Per 
Device CALs and Per User CALs.

Per Device CALs - Use this CALs option, if one device would be used by 
multiple users at different times. For Eg. People working in different 
shifts share the same computer to get connected to the SQL server. So in 
this case it would be economical to go for the Per Device CALs.

Alternatively,
Per User CALs - Use this CALs option, if the same user would be connecting 
to the SQL Server simultaneously from different Devices. For Eg. Developers 
who connect to the SQL server from the development machine and might also 
connect to the SQL server from the Test Machine. In this case it would be 
economical to go for the Per User CALs

You can also visit the following url to get answers to an exhaustive list 
of FAQs
 http://www.**--****.com/ 


HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights. 


Similar Threads:

1.SBS 2k CAL and SQL License

I have an old SBS 2000 box with SQL 2000 installed, for which I have CALs.  
On SQL, I want to deploy a browser-based timesheet application, using SQL as 
it's back end.

So, 
a.  Do I have the right to install and run SQL, and 
b.  Do the SBS CALs also cover users accessing the SQL DB?

TIA

2.Licensing Requirments from IIS5 server to SQL 2k server

On Thu, 21 Aug 2003 08:43:15 -0700, "John C."
< XXXX@XXXXX.COM > wrote:

>Are their additional licensing requirements when 
>connecting a front end IIS server to a backend SQL 2k 
>database server?

Same as if you had SQL on a normal server.  SQL CAL's for the accounts
accessing SQL, Windows CALs for those accessing the server.

Jeff

3.change license mode on SQL 2k cluster

I need to change the SQL server license mode on an installed SQL server
2000 cluster from processor license to per seat.

Does anyonw know?

4.Virtual Servers and SQL 2K Licensing?

We are running SQL Server 2000 Enterprise Edition [on
Windows 2003 EE] on our PRD SQL Server Cluster.  We have
two nodes, PRD1 and PRD2.  PRD1 will have one Virtual
Server [and corresponding named instance], and PRD2 will
have 3 Virtual Servers [and corresponding named instances].
 So, my question is: what are the SQL Server licensing
issues with running multiple Virtual Servers on a single
physical server?  

5.sql server 2k license

1. what's the difference between per seat and per proc?

2. If I install sql server on a 2 processor machine, I need 2 sql per proc 
license. right? If I instance the sql server to utilize more memory, I would 
need 4 (instead of 2) per proc licenses? Is that right?

6. sql 2k error 20089 Could not get license information correctly

7. change license mode on SQL 2k cluster

8. sms 2k3 enterprise edition and sql 2k licensing issues



Return to MS SQL SERVER

 

Who is online

Users browsing this forum: No registered users and 57 guest