By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,419 Members | 1,636 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,419 IT Pros & Developers. It's quick & easy.

SQL 2000/2005 Transaction Log Reader Library

P: n/a
Hi,

Is there any development library exist in the market for SQL Server
2000/2005 transaction log reader ? I need to use it for Capture Data
Change (CDC). Preferably Java.

Regards,

Feris
Sep 2 '08 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Wed, 3 Sep 2008 06:11:43 -0700 (PDT), Feris T wrote:
>Hi Hugo,

Thanks for the feedback. Actually I want to do incrementally update to
my data warehouse project using Java ETL tool. Since data capture
change using log is the most accurate I prefer this method.
Hi Feris,

I don't know who told you that data capture change using log is the most
accurate, but he was either not talking about SQL Server but about some
other database, or flat out wrong. (Or both). Microsoft has never
released documentation about the format of the log file, and there are
no libraries available for this.
Is there
any other workaround with SQL Server 2000/2005 ?
Probably, but since I'm unfamiliar with both data warehousing and with
ETL tools, I suggest you to post a new question. Probably best in a more
specialised newsgroup, such as microsoft.public.sqlserver.datawarehouse.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
Sep 3 '08 #2

P: n/a
Feris T (fe***@phi-integration.com) writes:
Thanks for the feedback. Actually I want to do incrementally update to
my data warehouse project using Java ETL tool. Since data capture
change using log is the most accurate I prefer this method. Is there
any other workaround with SQL Server 2000/2005 ?
It's difficult to say that something is accurte, when it is not supported.

There are third-party products out there that read the looks, but I
don't think they come with an API.

If you want to use CDC, I think your best option is to move to SQL 2008
which has such a feature.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Sep 3 '08 #3

P: n/a
Hi Hugo,

On Sep 4, 4:57*am, Hugo Kornelis
<h...@perFact.REMOVETHIS.info.INVALIDwrote:
>
Hi Feris,

I don't know who told you that data capture change using log is the most
accurate, but he was either not talking about SQL Server but about some
other database, or flat out wrong. (Or both). Microsoft has never
released documentation about the format of the log file, and there are
no libraries available for this.
Isn't it ? As the most accurate change for sophisticated database
system is resided in it's log.
>
Is there
any other workaround with SQL Server 2000/2005 ?

Probably, but since I'm unfamiliar with both data warehousing and with
ETL tools, I suggest you to post a new question. Probably best in a more
specialised newsgroup, such as microsoft.public.sqlserver.datawarehouse.
Yes, I've joined the newsgroup. Thank you for the info.

Regards,

Feris
Our Pentaho wiki : http://pentaho.phi-integration.com
Sep 4 '08 #4

P: n/a
Hi Erland,

On Sep 4, 4:52*am, Erland Sommarskog <esq...@sommarskog.sewrote:
>
It's difficult to say that something is accurte, when it is not supported..
Got your point. Thanks :)
>
There are third-party products out there that read the looks, but I
don't think they come with an API.

If you want to use CDC, I think your best option is to move to SQL 2008
which has such a feature.
It is based on this product that I come to a thinking of the same
workaround solution for previous version. Anyway, thanks Erland for
the update.

>
--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
Regards,

Feris
Our Pentaho wiki : http://pentaho.phi-integration.com
Sep 4 '08 #5

This discussion thread is closed

Replies have been disabled for this discussion.