dbTalk Databases Forums  

how to disconnect

microsoft.public.sqlserver.connect microsoft.public.sqlserver.connect


Discuss how to disconnect in the microsoft.public.sqlserver.connect forum.



Reply
 
Thread Tools Display Modes
  #31  
Old   
Eric Russell
 
Posts: n/a

Default RE: how to disconnect - 07-10-2008 , 01:25 PM






It sounds like more of a security and/or declarative data integrity issue.

#1 Do not grant access to users who don't need it. If an unwanted user has
access to the database due to their windows group membership, then instead
only grant access to specific accounts or deny access to specific accounts as
needed.
#2 Implement a primary key that would prohibit inserting duplicate data.
#3 Implement stored procedures to perform the inserts which includes
additional logic to prevent inserting unneeded data.
#4 Rather than granting users insert / update / delete permission, instead
grant them execute permission on the specific stored procedures they need.


"hui" wrote:

Quote:
I am working on SQL2000. Lately I find some users repeated executing INSERT
OR DELETE on SQL2000 remotely. May I disconnect these users when they
execute Insert operation 5 times? How can I relize it? Or may I disconnect
specified user by user name?

thanks

hui





Reply With Quote
  #32  
Old   
Eric Russell
 
Posts: n/a

Default RE: how to disconnect - 07-10-2008 , 01:25 PM






It sounds like more of a security and/or declarative data integrity issue.

#1 Do not grant access to users who don't need it. If an unwanted user has
access to the database due to their windows group membership, then instead
only grant access to specific accounts or deny access to specific accounts as
needed.
#2 Implement a primary key that would prohibit inserting duplicate data.
#3 Implement stored procedures to perform the inserts which includes
additional logic to prevent inserting unneeded data.
#4 Rather than granting users insert / update / delete permission, instead
grant them execute permission on the specific stored procedures they need.


"hui" wrote:

Quote:
I am working on SQL2000. Lately I find some users repeated executing INSERT
OR DELETE on SQL2000 remotely. May I disconnect these users when they
execute Insert operation 5 times? How can I relize it? Or may I disconnect
specified user by user name?

thanks

hui





Reply With Quote
  #33  
Old   
Eric Russell
 
Posts: n/a

Default RE: how to disconnect - 07-10-2008 , 01:25 PM



It sounds like more of a security and/or declarative data integrity issue.

#1 Do not grant access to users who don't need it. If an unwanted user has
access to the database due to their windows group membership, then instead
only grant access to specific accounts or deny access to specific accounts as
needed.
#2 Implement a primary key that would prohibit inserting duplicate data.
#3 Implement stored procedures to perform the inserts which includes
additional logic to prevent inserting unneeded data.
#4 Rather than granting users insert / update / delete permission, instead
grant them execute permission on the specific stored procedures they need.


"hui" wrote:

Quote:
I am working on SQL2000. Lately I find some users repeated executing INSERT
OR DELETE on SQL2000 remotely. May I disconnect these users when they
execute Insert operation 5 times? How can I relize it? Or may I disconnect
specified user by user name?

thanks

hui





Reply With Quote
  #34  
Old   
Eric Russell
 
Posts: n/a

Default RE: how to disconnect - 07-10-2008 , 01:25 PM



It sounds like more of a security and/or declarative data integrity issue.

#1 Do not grant access to users who don't need it. If an unwanted user has
access to the database due to their windows group membership, then instead
only grant access to specific accounts or deny access to specific accounts as
needed.
#2 Implement a primary key that would prohibit inserting duplicate data.
#3 Implement stored procedures to perform the inserts which includes
additional logic to prevent inserting unneeded data.
#4 Rather than granting users insert / update / delete permission, instead
grant them execute permission on the specific stored procedures they need.


"hui" wrote:

Quote:
I am working on SQL2000. Lately I find some users repeated executing INSERT
OR DELETE on SQL2000 remotely. May I disconnect these users when they
execute Insert operation 5 times? How can I relize it? Or may I disconnect
specified user by user name?

thanks

hui





Reply With Quote
  #35  
Old   
Eric Russell
 
Posts: n/a

Default RE: how to disconnect - 07-10-2008 , 01:25 PM



It sounds like more of a security and/or declarative data integrity issue.

#1 Do not grant access to users who don't need it. If an unwanted user has
access to the database due to their windows group membership, then instead
only grant access to specific accounts or deny access to specific accounts as
needed.
#2 Implement a primary key that would prohibit inserting duplicate data.
#3 Implement stored procedures to perform the inserts which includes
additional logic to prevent inserting unneeded data.
#4 Rather than granting users insert / update / delete permission, instead
grant them execute permission on the specific stored procedures they need.


"hui" wrote:

Quote:
I am working on SQL2000. Lately I find some users repeated executing INSERT
OR DELETE on SQL2000 remotely. May I disconnect these users when they
execute Insert operation 5 times? How can I relize it? Or may I disconnect
specified user by user name?

thanks

hui





Reply With Quote
  #36  
Old   
Eric Russell
 
Posts: n/a

Default RE: how to disconnect - 07-10-2008 , 01:25 PM



It sounds like more of a security and/or declarative data integrity issue.

#1 Do not grant access to users who don't need it. If an unwanted user has
access to the database due to their windows group membership, then instead
only grant access to specific accounts or deny access to specific accounts as
needed.
#2 Implement a primary key that would prohibit inserting duplicate data.
#3 Implement stored procedures to perform the inserts which includes
additional logic to prevent inserting unneeded data.
#4 Rather than granting users insert / update / delete permission, instead
grant them execute permission on the specific stored procedures they need.


"hui" wrote:

Quote:
I am working on SQL2000. Lately I find some users repeated executing INSERT
OR DELETE on SQL2000 remotely. May I disconnect these users when they
execute Insert operation 5 times? How can I relize it? Or may I disconnect
specified user by user name?

thanks

hui





Reply With Quote
  #37  
Old   
Eric Russell
 
Posts: n/a

Default RE: how to disconnect - 07-10-2008 , 01:25 PM



It sounds like more of a security and/or declarative data integrity issue.

#1 Do not grant access to users who don't need it. If an unwanted user has
access to the database due to their windows group membership, then instead
only grant access to specific accounts or deny access to specific accounts as
needed.
#2 Implement a primary key that would prohibit inserting duplicate data.
#3 Implement stored procedures to perform the inserts which includes
additional logic to prevent inserting unneeded data.
#4 Rather than granting users insert / update / delete permission, instead
grant them execute permission on the specific stored procedures they need.


"hui" wrote:

Quote:
I am working on SQL2000. Lately I find some users repeated executing INSERT
OR DELETE on SQL2000 remotely. May I disconnect these users when they
execute Insert operation 5 times? How can I relize it? Or may I disconnect
specified user by user name?

thanks

hui





Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.