SQL Server Licensing

[theoxyde]

The title is deceptive because this is an ethics question.

I am running a SQL Server 2000 database and we have a total of 30 Client Access Licenses. This particular database is the back end for a third-party application that connects to SQL Server via ODBC and is used by a total of 23 users. My problem is thus:

1. The third party application does not propery close its connections, and SQL Server does not properly clean up these connections for several hours. I cannot duplicate this problem myself as any connection I leave open SQL Server will tidy up after only a few minutes.

2. Because of the connections not being cleaned up, users will often get a message that SQL Server has reached its limit of licenses and will not allow them to log in. This is a daily problem and I must manually kill the dead connections for anyone else to be able to log in.

3. This problem has reached the attention of management and I have been instructed to "fix" the problem, but without spending anything.

4. The vendor for the third-party application says this is a documented problem with their software, but lays the blame on SQL Server (which my experience tells me is bullsh**). There will be no updates to solve this problem.

One possible solution that I have explored is running SQL Server in "per processor" license mode. This mode solves the problem (because of unlimited connections), but begs an the question: Can I ethically run SQL Server in "per processor" mode (for which licenses are much more expensive than our current scheme) to solve this problem since we have enough CALs to go around?

 

[dwarfthrower]

What is ethical to you is up to your own ethical standards (despite what some will try and tell you). I say pass the buck - Management told you to fix it. Inform them of your possible solution and any legal/ethical concerns you have about it. If they instruct you to go ahead, the Nuremberg defence is yours for the taking.

 

[Stevehewitt]

To be honest, I am dead agaist the entire CAL thing from MS anyway. I mean, I've purchased the Server software at £1500 (SQL and Windows), I've paid £500 for the client (Access and Windows) and you want me to pay for the right to connect to the server?!

Anyway, enough said. This isn't what this forum is for.

Back to your post. I agree with Dwarfthrower. Look at the options, looks at the costs and tell the management. To be honest though, knowing management they will probably not care about ethics.

I would talk to the supplier of the desktop software. Sounds like its their fault. I can't say I have heard of Access having this problem.

 

[theoxyde]

Thanks for the feedback. Since we have enough CALs, I'm not going to lose any sleep over it. If our MS rep has a problem with it, he can make his own suggestions... or we can run MySQL in the future.