Limiting number of database connections per user

Hello,
I would like to find out if it is possible in SQL Server 2000 to limit the
number of concurrent database connections per user. I am new to SQL Server,
and not sure if it is possible to limit it through some sort of parameter.
Any help would be greatly appreciated.
Thank you,
DmitriyNo way to limit the number of concurrent database connections PER USER.
Use the user connections option to specify the maximum number of
simultaneous user connections allowed on Microsoft? SQL Server
use SELECT @.@.MAX_CONNECTIONS to determine the maximum number of user
connections that your system allows
see "Setting Configuration Options" in BOL
Aleksandar Grbic
MCDBA, Senior Database Administrator
"Dmitriy" wrote:

> Hello,
> I would like to find out if it is possible in SQL Server 2000 to limit the
> number of concurrent database connections per user. I am new to SQL Server
,
> and not sure if it is possible to limit it through some sort of parameter.
> Any help would be greatly appreciated.
> Thank you,
> Dmitriy|||Thank you for your quick response.
Spasibo,
Dima
"Aleksandar Grbic" wrote:
> No way to limit the number of concurrent database connections PER USER.
> Use the user connections option to specify the maximum number of
> simultaneous user connections allowed on Microsoft? SQL Server
> use SELECT @.@.MAX_CONNECTIONS to determine the maximum number of user
> connections that your system allows
> see "Setting Configuration Options" in BOL
>
>
> --
> Aleksandar Grbic
> MCDBA, Senior Database Administrator
>
> "Dmitriy" wrote:
>|||Hi
you can use the table "sysprocesses" to get the information abt the
connections to the database , and there by u can restrict each users
programatically
Renjith
"Dmitriy" wrote:

> Hello,
> I would like to find out if it is possible in SQL Server 2000 to limit the
> number of concurrent database connections per user. I am new to SQL Server
,
> and not sure if it is possible to limit it through some sort of parameter.
> Any help would be greatly appreciated.
> Thank you,
> Dmitriy

limited number of connections to SQLMobile?

Using System.Data.SqlClient is there a limit to the number of connections an application can have to a SQLMobile dB?

If you have a look at the url below, it says "A device can only have a small number of connections to an instance of SQL Server at any time"

Does this mean 2, or 8 or what?
Should a app try to use only 1 connection throughout, or can we get away with 2-3?
Is this the same on WM5.0/PPP2003?

Any advice in this area much appreciated!

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlce/htm/_lce_sqlclient_705.asp

p.s. I'm not interested in connection pooling!

Connections to SQL Mobile have little in common with connections to SQL Server. First, the managed provider for SQL Mobile is System.Data.SqlServerCe, which is a different creature than the SqlClient you refer to in your post (which is used to connect to an instance of SQL Server).

Yes, you can have multiple connections to a SQL Mobile database. System.Data.SqlServerCe does not support pooling or encryption of connection strings however.

I am not aware of a limit to the number of SqlCeConnections you can have open against a single SQL Moble database, but if there is one it is more than a dozen as I have done benchmarking with more than this.

Darren

limited connections on the developer edition

hi all,

I installed sql server developer edition on

xp box. created a new ssis project and

then when i right click on control flow

then click new connections

i see only limited connection available.

how can i install the other connection option

such as oledb. etc.

thanks

joey

got it

my integration service

is running with limited rights

Limit to number of connections to the SQLCLR?

Is there a limit to the number of connections that can be made to the SQLCLR? If so, what is that limit and is it adjustable?

Thanks!

If you are referring to the way prior versions of MSDE 2000 were limited to 25 concurrent connections the answer is no.

Hope that helps. Let us know if you have any further questions.

|||

No, I am referring to access to the SQLCLR from any edition of SQL Server 2005. 2005 does not by default limit the number of user connections to the SQL Server instance. Internally to SQL Server, is there a limit to how many connections to the SQLCLR that can be made?

So for example, if had 1,000 connections open to SQL Server, will I be limited to only 200 (or some number) of them accessing SQLCLR procedures? Or, assuming server resources are adequate, can an unlimited number of clients access SQLCLR procedures concurrently?

|||You cannot specify a hard limit of concurrent users of CLR in SQL. You will get as many CLR users as your resources permit.

Limit to number of connections to the SQLCLR?

Is there a limit to the number of connections that can be made to the SQLCLR? If so, what is that limit and is it adjustable?

Thanks!

If you are referring to the way prior versions of MSDE 2000 were limited to 25 concurrent connections the answer is no.

Hope that helps. Let us know if you have any further questions.

|||

No, I am referring to access to the SQLCLR from any edition of SQL Server 2005. 2005 does not by default limit the number of user connections to the SQL Server instance. Internally to SQL Server, is there a limit to how many connections to the SQLCLR that can be made?

So for example, if had 1,000 connections open to SQL Server, will I be limited to only 200 (or some number) of them accessing SQLCLR procedures? Or, assuming server resources are adequate, can an unlimited number of clients access SQLCLR procedures concurrently?

|||You cannot specify a hard limit of concurrent users of CLR in SQL. You will get as many CLR users as your resources permit.

Limit to connections in sql express 05?

If I deploy a database to the web using sql express 05 is there a limit to the number of connections that can be made on it? I have read posts stating that but cant find any documentation from MSFT that supports that idea. I just know that it has a limit of a db size to 4 gigs.

Thanks!

SQL 2005 Express does not have a connection limit like MSDE did. 4 GB database and 1 GB RAM limits. It's in Books Online if you installed it.

Jeff

|||cool thanks Jeff.|||

jeff@.zina.com:

SQL 2005 Express does not have a connection limit like MSDE did. 4 GB database and 1 GB RAM limits. It's in Books Online if you installed it.

Jeff

|||

argh I hate not being able to edit! So if i deploy a website to the WWW built with VS Standard edition and a sql express db and it becomes wildly successful, will it be hard to upgrade the express db to a enterprise or standard db so that the website continues to function? I could just buy the license and then?...

Thanks.

|||

You can normally just attach the Express database in the new SQL. You may have to change a connection string, but even that may simply work for you.

Jeff

Limit remote connections

Hi,
We use SQL server 2000 on windows 2003. We usually use remote desktop to
connect to the SQL server. For security reasons, only 2 concurrent remote
desktop connections are allowed. I just noticed I'm able to use 'osql'
command to open as many connections to the SQL server as I want. Should I be
concerned? How other people deal with remote connections?
Thanks in advance,
Bing
Hello, Bing
In my opinion, the limit of 2 concurrent remote desktop connections on
Windows 2003 is for licensing reasons, not for security reasons.
Having an unlimited number of connections to SQL Server is no cause of
concern for security reasons, as long as each connection is properly
authentificated and comes from an authorised user and/or computer.
Razvan
|||On Jun 2, 1:33 pm, Razvan Socol <rso...@.gmail.com> wrote:
> Hello, Bing
> In my opinion, the limit of 2 concurrent remote desktop connections on
> Windows 2003 is for licensing reasons, not for security reasons.
> Having an unlimited number of connections to SQL Server is no cause of
> concern for security reasons, as long as each connection is properly
> authentificated and comes from an authorised user and/or computer.
> Razvan
However, you can limit the number of connections on an instance of SQL
Server, by using the "user connections" option. By default, SQL Server
allows a maximum of 32,767 user connections, but the actual number of
user connections allowed also depends on the limits of your
applications and hardware. Using the "user connections" option, you
can limit the number of connections to any desired number (less than
32,767), but this is done for performance reasons, not for security
reasons.
Razvan

Limit remote connections

Hi,
We use SQL server 2000 on windows 2003. We usually use remote desktop to
connect to the SQL server. For security reasons, only 2 concurrent remote
desktop connections are allowed. I just noticed I'm able to use 'osql'
command to open as many connections to the SQL server as I want. Should I b
e
concerned? How other people deal with remote connections?
Thanks in advance,
BingHello, Bing
In my opinion, the limit of 2 concurrent remote desktop connections on
Windows 2003 is for licensing reasons, not for security reasons.
Having an unlimited number of connections to SQL Server is no cause of
concern for security reasons, as long as each connection is properly
authentificated and comes from an authorised user and/or computer.
Razvan|||On Jun 2, 1:33 pm, Razvan Socol <rso...@.gmail.com> wrote:
> Hello, Bing
> In my opinion, the limit of 2 concurrent remote desktop connections on
> Windows 2003 is for licensing reasons, not for security reasons.
> Having an unlimited number of connections to SQL Server is no cause of
> concern for security reasons, as long as each connection is properly
> authentificated and comes from an authorised user and/or computer.
> Razvan
However, you can limit the number of connections on an instance of SQL
Server, by using the "user connections" option. By default, SQL Server
allows a maximum of 32,767 user connections, but the actual number of
user connections allowed also depends on the limits of your
applications and hardware. Using the "user connections" option, you
can limit the number of connections to any desired number (less than
32,767), but this is done for performance reasons, not for security
reasons.
Razvan

Limit remote connections

Hi,
We use SQL server 2000 on windows 2003. We usually use remote desktop to
connect to the SQL server. For security reasons, only 2 concurrent remote
desktop connections are allowed. I just noticed I'm able to use 'osql'
command to open as many connections to the SQL server as I want. Should I be
concerned? How other people deal with remote connections?
Thanks in advance,
BingHello, Bing
In my opinion, the limit of 2 concurrent remote desktop connections on
Windows 2003 is for licensing reasons, not for security reasons.
Having an unlimited number of connections to SQL Server is no cause of
concern for security reasons, as long as each connection is properly
authentificated and comes from an authorised user and/or computer.
Razvan|||On Jun 2, 1:33 pm, Razvan Socol <rso...@.gmail.com> wrote:
> Hello, Bing
> In my opinion, the limit of 2 concurrent remote desktop connections on
> Windows 2003 is for licensing reasons, not for security reasons.
> Having an unlimited number of connections to SQL Server is no cause of
> concern for security reasons, as long as each connection is properly
> authentificated and comes from an authorised user and/or computer.
> Razvan
However, you can limit the number of connections on an instance of SQL
Server, by using the "user connections" option. By default, SQL Server
allows a maximum of 32,767 user connections, but the actual number of
user connections allowed also depends on the limits of your
applications and hardware. Using the "user connections" option, you
can limit the number of connections to any desired number (less than
32,767), but this is done for performance reasons, not for security
reasons.
Razvan

limit per user/per db

Hello
I know that SQL 2000 has no way to set a limit for connections,
transactions memory or cpu per user or per db... but, there is a third
party software or any method that would allow a sysadmin to limit a
single db or a user?
ThanksWhat about ALTER DATABASE and the SINGLE_USER or RESTRICTED_USER options ?
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

limit per user /db on SQL 2005

Hello
is there any kind of limit (connections, transactions, memory, cpu)
that can be enforced per user or per db on sql 2005 ?
Thanks
Not really. If you have multiple SQL instances you can limit resources to
each instance (or app) via WSRM which is a windows 2003 feature.
Andrew J. Kelly SQL MVP
"xav" <xavierdaull@.gmail.com> wrote in message
news:1182700179.995006.253820@.n2g2000hse.googlegro ups.com...
> Hello
> is there any kind of limit (connections, transactions, memory, cpu)
> that can be enforced per user or per db on sql 2005 ?
> Thanks
>
|||Except for with sp2, you can limit number of connections using logon triggers.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OWy109ntHHA.3404@.TK2MSFTNGP03.phx.gbl...
> Not really. If you have multiple SQL instances you can limit resources to each instance (or app)
> via WSRM which is a windows 2003 feature.
> --
> Andrew J. Kelly SQL MVP
> "xav" <xavierdaull@.gmail.com> wrote in message
> news:1182700179.995006.253820@.n2g2000hse.googlegro ups.com...
>
|||> Except for with sp2, you can limit number of connections using logon triggers.
And how can I do it ?
|||By doing a ROLLBACK inside the trigger.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"xav" <xavierdaull@.gmail.com> wrote in message
news:1182862582.329249.214220@.w5g2000hsg.googlegro ups.com...
> And how can I do it ?
>
|||Thank you for your help.
Exemple found at: http://decipherinfosys.wordpress.com/2007/05/02/logon-triggers-in-sql-server-2005-sp2/
*Create a very simple login trigger */
create trigger AuditLogin_Demo
/* server means instance level*/
on all server
with execute as self
/* We specify the logon event at this stage
- If there are more than one connections,
- Issue a rollback*/
for logon
as begin
IF ORIGINAL_LOGIN()= 'AuditLogin' AND
(SELECT COUNT(*) FROM sys.dm_exec_sessions
WHERE is_user_process = 1 AND
original_login_name = 'AuditLogin') > 1
ROLLBACK;
end
go

limit per user /db on SQL 2005

Hello
is there any kind of limit (connections, transactions, memory, cpu)
that can be enforced per user or per db on sql 2005 ?
ThanksNot really. If you have multiple SQL instances you can limit resources to
each instance (or app) via WSRM which is a windows 2003 feature.
Andrew J. Kelly SQL MVP
"xav" <xavierdaull@.gmail.com> wrote in message
news:1182700179.995006.253820@.n2g2000hse.googlegroups.com...
> Hello
> is there any kind of limit (connections, transactions, memory, cpu)
> that can be enforced per user or per db on sql 2005 ?
> Thanks
>|||Except for with sp2, you can limit number of connections using logon trigger
s.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OWy109ntHHA.3404@.TK2MSFTNGP03.phx.gbl...
> Not really. If you have multiple SQL instances you can limit resources to
each instance (or app)
> via WSRM which is a windows 2003 feature.
> --
> Andrew J. Kelly SQL MVP
> "xav" <xavierdaull@.gmail.com> wrote in message
> news:1182700179.995006.253820@.n2g2000hse.googlegroups.com...
>|||> Except for with sp2, you can limit number of connections using logon trigg
ers.
And how can I do it ?|||By doing a ROLLBACK inside the trigger.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"xav" <xavierdaull@.gmail.com> wrote in message
news:1182862582.329249.214220@.w5g2000hsg.googlegroups.com...
> And how can I do it ?
>|||Thank you for your help.
Exemple found at: http://decipherinfosys.wordpress.co...erver-2005-sp2/
*Create a very simple login trigger */
create trigger AuditLogin_Demo
/* server means instance level*/
on all server
with execute as self
/* We specify the logon event at this stage
- If there are more than one connections,
- Issue a rollback*/
for logon
as begin
IF ORIGINAL_LOGIN()= 'AuditLogin' AND
(SELECT COUNT(*) FROM sys.dm_exec_sessions
WHERE is_user_process = 1 AND
original_login_name = 'AuditLogin') > 1
ROLLBACK;
end
go

limit per user /db on SQL 2005

Hello
is there any kind of limit (connections, transactions, memory, cpu)
that can be enforced per user or per db on sql 2005 ?
ThanksNot really. If you have multiple SQL instances you can limit resources to
each instance (or app) via WSRM which is a windows 2003 feature.
--
Andrew J. Kelly SQL MVP
"xav" <xavierdaull@.gmail.com> wrote in message
news:1182700179.995006.253820@.n2g2000hse.googlegroups.com...
> Hello
> is there any kind of limit (connections, transactions, memory, cpu)
> that can be enforced per user or per db on sql 2005 ?
> Thanks
>|||Except for with sp2, you can limit number of connections using logon triggers.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OWy109ntHHA.3404@.TK2MSFTNGP03.phx.gbl...
> Not really. If you have multiple SQL instances you can limit resources to each instance (or app)
> via WSRM which is a windows 2003 feature.
> --
> Andrew J. Kelly SQL MVP
> "xav" <xavierdaull@.gmail.com> wrote in message
> news:1182700179.995006.253820@.n2g2000hse.googlegroups.com...
>> Hello
>> is there any kind of limit (connections, transactions, memory, cpu)
>> that can be enforced per user or per db on sql 2005 ?
>> Thanks
>|||> Except for with sp2, you can limit number of connections using logon triggers.
And how can I do it ?|||By doing a ROLLBACK inside the trigger.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"xav" <xavierdaull@.gmail.com> wrote in message
news:1182862582.329249.214220@.w5g2000hsg.googlegroups.com...
>> Except for with sp2, you can limit number of connections using logon triggers.
> And how can I do it ?
>|||Thank you for your help.
Exemple found at: http://decipherinfosys.wordpress.com/2007/05/02/logon-triggers-in-sql-server-2005-sp2/
*Create a very simple login trigger */
create trigger AuditLogin_Demo
/* server means instance level*/
on all server
with execute as self
/* We specify the logon event at this stage
- If there are more than one connections,
- Issue a rollback*/
for logon
as begin
IF ORIGINAL_LOGIN()= 'AuditLogin' AND
(SELECT COUNT(*) FROM sys.dm_exec_sessions
WHERE is_user_process = 1 AND
original_login_name = 'AuditLogin') > 1
ROLLBACK;
end
go