In many business systems, especially those in an enterprise context, it is at
the very least good practice to implement some sort of audit trail. We need
to keep track of who has performed what operations and when they occurred. In
addition, we may require information not only on the underlying database
table affected, but also on the individual field changes themselves. This
article will look at implementing an audit table in an SQL Server database
that automatically tracks the changes made to a dataset when its updates are
sent back to the data store.
Trigger Happy
Triggers are most commonly used to log the audit trail of user activity. They
can be powerful in this regard, but they are not completely free of issues.
For one thing, triggers are database-specific. In add... (more)
Prior to .NET, DCOM existed as Microsoft's solution to remote object access.
This technology leveraged the successful COM architecture to provide an
infrastructure for remote communication. However, DCOM suffered from a
variety of drawbacks and difficulties, and it ultimately led to Microsoft's
spirited drive to develop Web services and their associated standards.
Unfortunately, in the pr... (more)