Groups | Blog | Home
all groups > sql server new users > september 2006 >

sql server new users : Is there something like a completely external trigger to catch updates?


karen
9/26/2006 9:37:19 AM
Hi-
We need to find out when records are added or changed in a vendor's database
for a customer. The customer has said that we can't add triggers nor make
other changes to their database. I've been familiar in the past with SQL
databases (Oracle, Informix), but haven't been using them currently. My
boss thinks that there is a way for us to write a .dll in VC++ that can
somehow tell when records in a SQL-Server DB have changed.

So, we're allowed to read their database, and we're allowed to install
software on the same machine. But, we're not allowed to create any triggers
(which could go away when their vendor provided updates). Is there some way
to intercept those updates without making any changes in the SQL-Server DB
itself? They currently have SQL-Server 2000, and plan on upgrading to 2005
sometime in the next year or so.

At least one of the tables that I need information on does not have a
datetime added/updated field, so I can't just read the table and search for
new/updated records since the last time read.

(Is there a better newsgroup to ask this question? It's not a new user
question, but I'm certainly in the new user category.)

Thank you for any direction that you can provide.

-karen

Arnie Rowland
9/26/2006 9:44:43 AM
There are third party tools that read the transaction log file, and log data
changes from there. If they can create the functionality, I don't see why
you can't -if the skills are available. However, even the log file format
can change when there is a product upgrade, so you may have to periodically
upgrade your log reader also.

Look for:
Lumigent SQL Server log explorer
ApexSQL Log Navigator
Log P.I.
SQL Log Rescue from red-gate


--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


[quoted text, click to view]

karen
9/26/2006 9:49:22 AM
Thank you, I'll look into them. Unfortunately, the skills certainly aren't
here right now. I guess that just makes it more of a challange.

-karen

[quoted text, click to view]

Roger Wolter[MSFT]
9/26/2006 11:32:56 AM
A cheaper and easier alternative would be to use the SQL Server trace
function to trace commands to a file and then periodically look through the
file for changes. You should be able to limit the trace to only what you
care about.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

[quoted text, click to view]

AddThis Social Bookmark Button