SQL server 6.5 - License revoking

Posted on 2004-11-09
Last Modified: 2011-10-03
We are running MS SQL Server 6.5.
I have purchased licenses for 1000 users.
License manager is displaying 1650 users.
Should I revoke the extra entries from License manager? We are getting error entries in event viewer all the time.
Also, does this cause slowness of the database system? Recently, we start experiencing application slowness.
How the revokation of license will effect on the database? Those revoked users will be able to log in again or not?

Please advise.
Question by:wimzieguy
    LVL 18

    Expert Comment

    The licencing information is entirely seperate from SQL you could enter 1 billion licences and it would not hamper sql's performance.  obviously though if you had a billion simultanious connections sql would die.

    " We are getting error entries in event viewer all the time." this is usually caused when the licencing type has changed from per server to per seat it gets a bit confused.   The simplest thing is to delete all the licencing info and then put it in again which should stop it filling your event log.

    " we start experiencing application slowness"  Can you give us a bit more info on the volumes of concurrent connections & concurrently active connection + machine specs, etc as it is more lokely that either your db needs tuning or your overstrething the server.

    Author Comment

    How the deletion of licence information from license manager will effect the database? (if any)

    At this time, there are 358 idle connections and only 1 active connection.
    Machine = Compaq Quad processor, 1 GB RAM.

    How to tune the database? Are there specifics steps involved in database tuning?
    LVL 18

    Expert Comment

    SQL doesnt actually stop then there is insufficient licences.   It simply fills your event log with the annoying reminders.   so it wont have any effect, so long as you put them back afterwards (to stop the event log entries)

    Ok with 1GB of ram the OS is going to take most of that, leaving virtually nothing for SQL.   What memory SQL has will be eaten up by the large number of active connections.    You certainly need much more ram.   2GB for sql alone.     And on top of that I would suggest that your client application really should use connection pooling or at the very least close connections when they are not in use.    Each open connection uses memmory.

    Author Comment

    How to put license information back in license manager?

    We are on WIN NT 4.0 SP6. Do you still think that 1 GB RAM is not enough? We are running this particular application for past 6 years without any issues.

    How to check whether client application is using connection pooling or not?
    How to get rid of idle connections?
    LVL 18

    Expert Comment

    Off the top of my head I cant remember the licencing management tool for NT4   but essentially you would enter these as if they were new licences.

    With so many connections to SQL you need a lot of RAM.    To be absolutely honest also, I think you really should consider upgrading the OS and SQL.  Why?   SQL has vastly improved its query optimisation techniques since 6.5, and also NT4 + SQL6.5 are no longer supported by Microsoft.   Thus in the case of a disaster MS wont help you out.

    LVL 18

    Accepted Solution

    Do you need any more assistance with this question ?

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Enabling OSINT in Activity Based Intelligence

    Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

    When you hear the word proxy, you may become apprehensive. This article will help you to understand Proxy and when it is useful. Let's talk Proxy for SQL Server. (Not in terms of Internet access.) Typically, you'll run into this type of problem w…
    This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
    Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
    Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed

    779 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    12 Experts available now in Live!

    Get 1:1 Help Now