November 14, 2005 at 1:28 am
Hi, I'm new here. This is probably a very 'beginner' type of question but outside my knowledge and I would be grateful for some help. I've started work at a company where they still have NT4 Servers and SQL Server 6.5 as their database system. I'm responsible for maintaining the bespoke software that accesses the database and I've discovered that the Systems Administrator has no qualifications for his job and can't help me at all. They also have no DBA or anyone with database knowledge (he left). Additionally, I can find no manuals for 6.5 anywhere, so I'm on a very steep learning curve to try to understand a large problem.
According to the company, they have 25 licences, and around 23 PCs attached to the network, using the database. I have discovered that when a user runs the bespoke application it makes and retains two connections to the database while running. Additionally each user will run two, sometimes 3 copies of the software at the same time. Most of the time, although it doesn't run too slow, it is capable of supplying the users with the answers they require. On irregular but frequent occasions it slows down to a grind and instead of a response taking 2 or 3 seconds, it can take 30-60 seconds. Looking at the task manager, the Server is running at about 20% capacity, so the problem doesn't appear to be there. So I'm looking at the connection issue.
Sorry for the preamble. Now the questions. If 20 users run the software, does 6.5 say that there are 20 connections (for 20 users) or 40 connections (2 connections per software instance)? If they then run the app twice, does that now become 40 connections (for 2 users x 2 apps) or 80 connections (for 2 connections per 2 software instances x 20 users)? Does 6.5 happily allow this number of connections, but only allow 25 live/active connections?
I may be missing something you think is blindingly obvious through my lack of understanding, so any help you can give me will be gratefully received.
Regards, Mike.
November 16, 2005 at 2:50 am
Hi Mike
SQL 6.5 Has two licencing modes - Per Seat and Per server.
You should be able to find which one it is via the contol panel, Licencing manager I think? (Forgive the lack of clarity, it's been a while since I used 6.5/NT).
From memory, Per seat means a licence for each machine connecting to the server (so a max of 25 pc's for your company)
Per server means per connection (so a max of 25 connections at any one time)
In fairness though, I can't see Microsoft come hunting for anyone using 6.5 Illegally
Regards
Eoin
November 18, 2005 at 1:40 pm
Thanks Eoin,
I'm not concerned about Microsoft coming hunting. Just trying to find out why the system slows to a grind for no apparent reason, so I just wondered if the licencing would have anything to do with that. your response and a private email tells me that I'm looking in the wrong place.
Since posting the question i have discovered that the NT4 Server that acts as Primary Domain Controller has the max 2GB C: drive and it's been filled by the Sys Admin so that it only has 100MB free. I also discovered that the paging file is split into over 100 pieces and the MFT is over 1000. So although the database server is only running at around 15-20% the system is still going slow, but with the new evidence I may just focus my attention in the direction of the PDC at the present.
Again thanks for your help. It's much appreciated.
Mike.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply