Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Licensing question - local connections 1

Status
Not open for further replies.

paskuda

Programmer
Jan 27, 2005
104
PL
Hello,
I've been reading a little bit on SQL Server licensing issues and got a little bit confused.
Let's say I want to use Server license + CALs. I read that each machine connecting to SQL Server (or each user, depending on CAL type) needs a separate CAL. What should I do if all software connecting to SQL server resides on the same machine as the database engine ? Should I:
- just buy the SQL Server license ?
or
- buy the SQL licence AND use one per device CAL ?
Actually I've started digging through licensing issues this morning, so excuse me if the question is stupid :)

Cheers,
Michal
 
Will users to connecting to the application and viewing the data via the application?

What it basically comes down to is any user who will be viewing the data that's in the SQL Server will need a CAL.

Here's my FAQ on SQL licensing faq962-5153.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
OK, so I'll try to describe the problem.
We have some shops spread all over the country + one central location where all the stock data are kept.
The machine in central location (SERVER) allows terminal connections from shops (CLIENTS) and also has database engine installed.
In the morning shops connect to the server using terminal services and clerks start POS (point of sale) application - this is the application that connects to the SQL server. Also, on the SERVER we have some other applications that require DB access.
The OS running on SERVER in Windows 2003 + Terminal Services, of course all the shops have Windows Server CALs and Terminal Server CALs. The database engine is MS SQL Server 2000.

Now, the problem itself.
Since the users from remote locations connect to the SERVER using terminals and start the application, that connects to the database, locally on the server machine - do they need SQL CALs ? It IS a fact, that they see the output in remote locations BUT they already payed for TS CALs, and the idea of terminal services is to allow local-like work (I guess). Isn't it just enough to buy ONE SQL CAL (per device) for the SERVER machine, since physically all the DB connections are from localhost ?

I hope you'll be able to understand any of above, seems it's harder to describe than I thought :)

Michal
 
Nope, that would be cheeting. The device that the user is using isn't the server, it's actualy the machine in the shop. You'll need a device CAL for each terminal in the shops which connect via Terminal Services.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Thanks Denny. I'll check the other sources too, but what you write seems to make sense :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top