No. of connections to the SQL Server

Question

No. of connections to the SQL Server

Anand-407418

SSC Enthusiast

Points: 181
More actions
February 12, 2007 at 4:42 am

#62536

Hi folks,
I have a system wherein I need to connect a server with many clients(or vice-versa). However right now what is happening is that only 2 clients are being able to connect to the Server. The other clients simply say that the Server does not exist or Access Denied.
Is there any way of solving this issue or configuring such a setting?
Please let me know ASAP.
TIA
Anand

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Sugesh Kumar One Orange Chip Points: 27311 More actions · Answer 1

Right click the server and use the following options to check and configure the connections properties in your sql server.

Right click the server, goto connections and set a value of your requirement in the max number of connections property.

Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com

Anand-407418 SSC Enthusiast Points: 181 More actions · Answer 2

Where do i right click it from? Enterprise MAnager? If so then ive already tried taht and there is no such property there.

Anand-407418 SSC Enthusiast Points: 181 More actions · Answer 3

In the properties there is a Connections TAB but the no. is set to 0 (i.e. Unlimited) there. Still i am facing this issue.

colin.Leversuch-Roberts SSC Guru Points: 52643 More actions · Answer 4

which edition of sql server and o/s are you using - just in case it's developer which is connection limited.

Are you certain your connections are correct as this sounds like a client issue rather than a server one.

[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/

Lowell SSC Guru Points: 323518 More actions · Answer 5

I agree with Colin; Server does not exist or Access Denied. is typically the application cannot connect, and has nothing to do witht he number of allowed connections. A different error message appears if the connection was attempted and then refused due to licensing.

unable to connect could mean a lot of things:

the client machine cannot resolve SERVERNAME via TCPIP or named pipes (same network?); try putting in the IP address of the server instead of the name. could even be a misspelled name of the server as well.

different versions of MDAC might affect this...especially true if the developer can connect, but not a client machine that was nto set up with an MSI or something.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Anand-407418 SSC Enthusiast Points: 181 More actions · Answer 6

Hi guys,

I am using SQL Server 2000 on Windows Server 2003 Enterprise Edition.(SP1)

The reason why i am suggesting the issue of only 2 connections is coz,

Say i have the following config:

Server Machine, Clients A,B,C. Now i can connect the clients A,B at one time to the Server, and connect Clients A,C at one time but never Clients A,B,C.

i.e. At one instance of time i am able to see and connect to the Server from the Enterprise Manager of Clients A,B and at one time from clients A,C. But never from all 3.

SO let me know incase ou have any more suggestions to this.

THanks a ton.

Wilbur Sean Bvuma SSC-Addicted Points: 425 More actions · Answer 7

Hi

Are you trying to Log into the Windows Server Box or to the SQL Server ?

Reason I have the same thing where there is a limited amount of users That can Log into a server,

So is this problem ?

Wbiggy

Anand-407418 SSC Enthusiast Points: 181 More actions · Answer 8

Hi Wilbur,

Did not really understand your first question, I am trying to connect to the SQL Server on my Server Machine via the Enterprise Manager on the CLient Machines.

However the issue may be related to the OS(as i have come to think about now) but am not really sure of that.

WHat was the problem that you faced, and what was the solution?

Thanks

Wilbur Sean Bvuma SSC-Addicted Points: 425 More actions · Answer 9

ok with my problems, I connect to another machine using Remote Desktop Connection, and if there is many users I would call the Server Admin and tell the other people to Log off the machine, or I could just run this command "%SystemRoot%\system32\mstsc.exe /console" and it would log in no matter how many users were logged into the Box,

another thing which I saw in SQL 2005, is that you can limit the number of connection made to the Server, I was trying to see if I could see it SQL 2000 Interprise, but am not getting lucky, I'll keep on looking for a way for you

So hopefully maybe this can help

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 10

When using RDP, only 2 users can connect simultaneously. If you use the /CONSOLE switch you can get 3 users. If you want to see who is logged on you can use the tsadmin command.

Now, let me address what I believe to be a misunderstanding. Users, whether they be application software users of developers do not need to connect (log in) to the Windows server where SQL Server is installed directly. For developers, you can install the client tools (Enterprise Manager, Query Analyzer, etc) locally on their client computers. This will allow them all the access needed to SQL Server. As for user applications the same principle applies.

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."