Interesting subject to be sure. I have MS SQL 2000. Normally my users are
logged in via Terminal Services. So to kill off the users I would log them
off via TM Manager.
However, I now have some FAT clients that do not use TS. I can see the
processes in EM under Management - Current Activity - Process Info. Would I
kill these processes to knock the users off the system? What happens to the
process on the client machine?
Any help would be great.
DG
Tibor Karaszi - 25 Jul 2008 15:25 GMT
"Killing" the users from Enterprise Manager - activity manager will execute the TSQL command KILL.
This is documented. It will terminate the SQL Server connect from the client's application. you say
you have FAT clients, and I assume by that you mean that you have exe files executing locally on the
client machine and this has a connection to SQL Server. So, whatever happens to the application
depends on how the programmer handles a lost connection to SQL Server. The app might bomb on next
request or silently do a re-connect - or anything in between...

Signature
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
> Interesting subject to be sure. I have MS SQL 2000. Normally my users are logged in via Terminal
> Services. So to kill off the users I would log them off via TM Manager.
[quoted text clipped - 6 lines]
>
> DG
Daniel Jameson - 25 Jul 2008 20:18 GMT
DG,
Why do you want to knock them out? For how long do you want them knocked
out? Do you need them out of the server completely, or just out of specific
databases?

Signature
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.org
> Interesting subject to be sure. I have MS SQL 2000. Normally my users
> are logged in via Terminal Services. So to kill off the users I would log
[quoted text clipped - 8 lines]
>
> DG