How the ODBC are licenced??

Question

Post reply

How the ODBC are licenced??

Jorge Gordillo

Old Hand

Points: 315
More actions
May 2, 2006 at 10:56 am

#112732

Hi !

If 10 PC use a local ODBC with the same user to conect to SQL Server, how the pc´s are look like?? each one as a client or how the licences works???

thanks

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Antares686 SSC Guru Points: 125444 More actions · Answer 1

Depends on the server they connect to and the licensing model you have setup. ODBC itself is not licensed perse.

SQLBill SSC Guru Points: 51440 More actions · Answer 2

You still have ten connections to the database. It doesn't matter if all connections use the same username or all different names - it's still ten connections. Your SQL Server license must allow that amount of connections.

-SQLBill

Jorge Gordillo Old Hand Points: 315 More actions · Answer 3

Ok, perfect.

THANKS

Now i have another question, the best to bought is the processor License, but i read on one link that also i need the licences for each conecction to the win2003 so another kind of license.....is that true, not only the SQL procesor- license also the win2003 license per user that use the SQl server???

Please help. i´m new on this

Jorge

Antares686 SSC Guru Points: 125444 More actions · Answer 4

Unless I missed something no if they need to connect to SQL Server only and you have a per processer license then you are fine. If however they need to connect to a website which in turn connects to SQL Server or need to connect to the box itself for file system access then you are looking at the OS license.

Eddie Wuerch SSChampion Points: 12535 More actions · Answer 5

http://www.microsoft.com/sql/howtobuy/default.mspx

You do not license connections to SQL Server. You license either (for SQL Server - the Win2003 license is separate and unrelated):

1. Per processor for unlimited clients from unlimited devices

- or -

2. Per server, plus a separate user CAL (client access license) for each person who will connect to the data: directly, through an application server (like a website), will receive emailed reports from an app that connects to the SQL server, etc. Each user is licensed for an unlimited number of connections to an unlimited number of local SQL Servers of the same edition from an unlimited number of devices (computers, PDAs, etc.). Note: each person needs their own CAL; CALs are not for concurrent usage, they are for any usage. If you have 100 users, but only ever have one connected at a time, you still need 100 CALs.

- or -

3. Per server, plus a separate device (computer/PDA/etc.) CAL for each device that will connect to the data. Each device is licensed for an unlimited number of users for unlimited number of connections to an unlimited number of servers of the same edition on the same local network.

So, if I understand your question correctly, you have one person, using 10 PCs to connect to a single SQL Server. The best scenario would be a single User CAL for the user, plus a single SQL Server server license for the server itself. Note: "User" here means "physical person", not "user account as defined on the server".

If I'm not reading your question correctly, and by "same user" you mean "same user/password account", but not the same person, then you would purchase a single SQL Server server license, and would look at either device CALs or user CALs to license either the computers (with an unlimited number of users) or the users themselves (who may then use an unlimited number of PCs to connect).

As for the Win2003 licensing, that is separate from the SQL licensing, and follows the same rules for connecting to Win2003 if no SQL Server were present. If you only purchase SQL Server processor/server/CAL licenses, and no separate Win2003 access licenses, then nobody is licensed to connect to your server. I'm guessing from the other responses to your question that last point is news to a number of folks. There are Windows Server user CALs and device CALs for named connections, and there is the Internet Connection License for running a public web server on Win2003. Have a look at the 'how to buy' pages for Windows Server 2003 for more info there.

-Eddie

Eddie Wuerch
MCM: SQL

Yelena Varshal SSC-Dedicated Points: 34286 More actions · Answer 6

You would also want to ask your IT department. In some companies Enterprise Agreement may include SQL client licenses into agreement as well as some other clients.

Regards,Yelena Varsha

Jorge Gordillo Old Hand Points: 315 More actions · Answer 7

THANKS

Really thanks for the answers and the help. now all is clear. =)

Is good to know and see that there outside are people that knows (as you) their busissness and want that help another that want to know and to do the correct things(Agreements) and not to have legal problems.

Have a Nice day-week-year

Thanks

Jorge

Jorge Gordillo Old Hand Points: 315 More actions · Answer 8

OK. just the last question....... =)

We bought the basic Box of SQL= "SQL server 2000 Std. 5 CLT".

But reading and learning, i need to buy the "License per processor" couse i need to conect to server about 150 Pc´s....(by the way all this is becouse i´m using a client program "ONBASE" by hyland" and ot connect to SQL via ODBC, so. i will have 150 users so it means 150 connections, so i thought the best is the processor license.

Now.... how can i make the upgrade or change..i have on contol panel the Sql Server 2000 licensing Setup, but i can just increase the Per Seat licences, not to change to Processor Mode....what did i need to do????

Thanks again =)

Jorge

Jorge Gordillo Old Hand Points: 315 More actions · Answer 9

sorry. one more( maybe i will make tons of questions jajaja)

My server has 2 processors, i know that is 1processor=1license... but is obligatory to bought 2 licenses couse it has both. or can i just bought 1 license and reduce the use to one procesor??

I dont know if i´m clear on my question

Thanks

Steve Jones - SSC Editor SSC Guru Points: 736232 More actions · Answer 10

The MS licensing states you must license every processor on the box where SQL runs, whether you have set affinity or now. This means 2 CPUs = 2 per processor licenses.

If you license per server or per seat, you do not license twice for CPUs.

Yelena Varshal SSC-Dedicated Points: 34286 More actions · Answer 11

Please see

http://www.microsoft.com/sql/howtobuy/processor.mspx

Processor Licensing Model

http://www.microsoft.com/sql/howtobuy/multicore.mspx

SQL Server Multicore Licensing Policy

The second link is if you have questions how to license a processor with 2 threads.

Regards,Yelena Varsha