Re: Database Auditing and connection strings
From: Paul Clement (UseAdddressAtEndofMessage_at_swspectrum.com)
Date: 12/23/04
- Next message: Miha Markic [MVP C#]: "Re: Connection String Property For Pooling"
- Previous message: dmac: "Connection String Property For Pooling"
- In reply to: GCeaser_at_aol.com: "Database Auditing and connection strings"
- Next in thread: GCeaser_at_aol.com: "Re: Database Auditing and connection strings"
- Reply: GCeaser_at_aol.com: "Re: Database Auditing and connection strings"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 23 Dec 2004 07:51:19 -0600
On 22 Dec 2004 09:55:58 -0800, GCeaser@aol.com wrote:
¤ All,
¤
¤ We have a need to be able to perform auditing on the database side
¤ of our application. As part of the requirement we must know the userid
¤ of the person performing the database modification.
¤
¤ All of the approaches that have been implemented at our organization so
¤ far, result in connection pooling not being taken advantage of. They
¤ are: 1) Using a standard ID and password in SQL Server but providing
¤ the userid in the app= connection string parameter 2) Using windows
¤ integrated authentication.
¤
¤ The goal is that we want the userid performing the transaction
¤ regardless of whether or not the modification is performed via the
¤ application of a direct database connection through some other tool.
¤ This indicates the need to use a trigger for the auditing.
¤
¤ One of the ideas I had was if the Stored Procedure that the application
¤ calls could set some SQL Server variable to the value of the userid,
¤ then the userid could be passed into the stored procedure as a
¤ parameter and each stored procedure would simply sent the userid
¤ variable and the trigger would check that variable first. If the
¤ variable was not populated, it would use the normal user id variable in
¤ SQL Server.
¤
¤ Any ideas or suggestions on this? (Note: We are using SQL Server
¤ 2000)
It might help us to understand your application configuration a bit better, such as the type of
application (ASP.NET? VB/C#.NET?). This might at least give us an idea as to why connection pooling
does not appear to be working for you.
Since the database can be accessed through different clients it would appear that you would likely
need to implement integrated authentication if you want to identify the user (via a trigger) who is
making the change.
Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)
- Next message: Miha Markic [MVP C#]: "Re: Connection String Property For Pooling"
- Previous message: dmac: "Connection String Property For Pooling"
- In reply to: GCeaser_at_aol.com: "Database Auditing and connection strings"
- Next in thread: GCeaser_at_aol.com: "Re: Database Auditing and connection strings"
- Reply: GCeaser_at_aol.com: "Re: Database Auditing and connection strings"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|