Re: sql server connections

From: Vadim (vadim_at_wisetrack.com)
Date: 06/20/03

  • Next message: bryn: "Re: builtin\administrators in the db_owner role" 
    Date: Thu, 19 Jun 2003 22:57:18 -0700

    Thank you for your reply.

    The problem occurs when clients are trying to connect to
    sql server 2000 on win2k, there are 2 programs running on
    the client machine each one uses ODBC connection, only one
    can connect and the second fails.
    Are there any known bugs in ODBC drivers on WinXp that
    would prevent 2 simultaneous connections?
    Or could this happen if system administrator restricted
    the user to certain amounts of connections?

    >-----Original Message-----
    >There is no restriction in sql server for that AFAIK.
    How are you
    >attempting to connect and what error are you getting?
    >
    >--
    >
    >Andrew J. Kelly
    >SQL Server MVP
    >
    >
    >"vadim" <vadimo@shaw.ca> wrote in message
    >news:jwlIa.264056$Vi5.6929454@news1.calgary.shaw.ca...
    >> Hi,
    >>
    >> It looks like I can not establish two simulatneous ODBC
    connections to the
    >> same Sql server
    >> from the same client machine.
    >> Are there any sql server settings that I should check
    to allow multiple
    >> connections from one machine?
    >>
    >> Thank you
    >>
    >> Vadim
    >>
    >>
    >
    >
    >.
    >

  • Next message: bryn: "Re: builtin\administrators in the db_owner role"

    Relevant Pages

    • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
      ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... communication between ODBC (OLEDB and Native Client, ... Every new client opens again 30 connections if I open 30 tables ...
      (microsoft.public.sqlserver.connect)
    • Re: SQL Server 2005 Express OLEDB Connection from VB6
      ... Thanks for getting me to read this again and realizing they meant the client ... I think we'll stick with ODBC, since there is less to install on the client ... Microsoft SQL Server Native Client ...
      (microsoft.public.sqlserver.connect)
    • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
      ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
      (microsoft.public.sqlserver.connect)
    • Re: Access link table security
      ... onerous chore of creating DSN's on each client. ... >and SQL Server is on the same machine. ... >How and where do I set at the Access frontend so that I can choose the login ... >change the login name for the Access frontend, do I need to play with ODBC ...
      (microsoft.public.sqlserver.security)
    • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
      ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
      (microsoft.public.sqlserver.connect)
    • Quantcast