Very Computer

1. logging failing login attempts

the xp_trace* commands allow me to log failing login attempts directly
to a table. I would, however, also like the IP-number in my log. There
is however only the Hostname column to stick to. I havent (cant) tried
to contact my server from outside my domain, so I dont know exactly how
specific SQL Server (I'm using 7.0) is about the hostname(.domain?).
I cannot relate to the sysprocesses table in a trigger in order to
retrieve further info, as the actual insert is performed by a
systemproces and (of course) not by the illegal login connection.
Isn't there anyway that I can retrieve more information of the remote
machine behind the failing login connection?
Im running the SQL Server on a win2000 server.

Thanks,
Bo

2. Building B-trees from the leaf nodes

3. Log user/password of fail connection attempts

4. NULL Fields and Prepared Statements

5. Logging/Auditing Failed Login Attempts?? does not work...

6. SQL 7 Standby server

7. LOG failing login attempts - how?

8. ODBCDirect and File DSN

9. Logging/Auditing Failed Login Attempts?? does not work...

10. Task from Step does not support joining distributed transactions or failed when attempting to join

11. Logging level changed after reboot, not after restart of IIS

12. Trigger-based audit logging to properly log old/new NULL

13. Issue NOTICE for attempt to raise lock level?