Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AlanS
Starting Member
28 Posts |
 Posted - 2005-05-04 : 12:30:36
|
| I need to capture continuing, but fairly simple, login/logout data, e.g., NT user name, SQL Server login name, login time, logout time. The data will be captured continuously, and periodically reviewed by administrative and security staff. Is SQL Profiler the easiest and simplest way to capture this information, or is there a better way? |
|
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2005-05-04 : 13:07:35
|
| Are you trying to capture users logging into the database or users logging into an application that uses the database?Mike"oh, that monkey is going to pay" |
 |
|
|
AlanS
Starting Member
28 Posts |
Posted - 2005-05-04 : 13:39:26
|
| Users will only log into a single administrative application, for which the database provides the back end. The application is an aspx.net application, developed in C#. Users will have no interaction with the database except through the application. |
|
|
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2005-05-04 : 13:59:43
|
| I don't think profiler would be the right way to got then. Something along the lines of forms authentication set to windows and pass along that info the db would be better. The logout would be unreliable however. You could create a Logout button and capture the user and time that way however that depends on the user clicking the logout button and not actually just closing the app down. Profiler really is meant more as a performance monitoring tool and really shouldn't be used to capture data for reporting/auditing.Mike"oh, that monkey is going to pay" |
|
|
|
|
|
|
|
|
how to capture login/logout data