SQL Server Licenses w/ADO connections

[Foada]

Does anyone have any links/info regarding how SQL server determines the license count required for ADO connections. Is it by client machine or by ADO connections. I am assuming that if I use NT Server authorization each client requires a single license and can have multiple ADO connections but I would like to confirm this. Thanks in advance. Anything is possible, the problem is I only have one lifetime.

 

[CasperTFG]

As far as I know with SQL Server, each Server requires a license, and the client side installations are unlimited.

Here is something from the On-Line docs.

Options
Licensing Mode

If accessing this dialog box from Control Panel, the mode chosen during setup is selected by default, along with the number of devices or processors you have previously selected.

Per Seat for

The Per Seat licensing mode requires a Client Access License for each device that will access SQL Server 2000 Server. Per Seat is often more economical for networks in which clients connect to more than one server.

In the edit box, select the number of devices to license.

Processor License for

With Processor licensing, a license is needed for each processor installed on the computer running SQL Server. The Processor License allows any number of devices to access the server, whether through an Intranet or over the Internet.

Using Processor licensing, SQL Server 2000 can take advantage of each installed processor, and support an unlimited number of client devices. A customer that provides access to SQL Server databases over the Internet, or that has a large number of users, will generally choose the Processor License.

In the edit box, select the number of processors to license.

Continue

Click the Continue button to complete the installation process, or after modifying the number of devices or processors you want to license.

Craig, mailto:sander@cogeco.ca

Remember not to name the Lambs...
It only makes the chops harder to swallow

 

[Foada]

Thanks for the info Craig. Any ideas about the ADO connection? I have used just an ODBC connection from client machines running NT Workstation, and after 10 connections NT will not allow you to make any more connections without getting NT server. I wanted to know if the same thing held true with ADO. I assume it would, but I am trying to put together a project budget and was hoping I could pick at some minds without setting the whole thing up to test it. Anything is possible, the problem is I only have one lifetime.