This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Log reader not supporting native compression!!?

Hi, I purchased Toad for SQL server professional to get the log reader functionality to read offline transaction log files instead of using SQL profiler to view the activity on the database, I now find that I cannot use it as we use native compression!! This makes this functionality useless to me, as we use compression across the board......

 

1. Who would not use native compression with their backups?

2. Do I now have to change all my backup maintenance plans to make use of this tool

 

This is very frustrating, why can't native compressed backups be accessed? Is this just a way to sell another product?

 

:(

Parents
  • Hello

    I would suggest using the next version of Litepseed (8.7) rather than TOAD for what you are trying to do.

    You are proably using the newest TOAD and not row compression or page compression in your database. But just simply a compressed backup (In this case version of SQL does not matter).
    It was not supported currently because Litespeed compression is the tool we recommend be used to created SQL compressed backups. Please note that Log reader is designed as a part of Litespeed first, but is shared with the TOAD team.

    Aagin I Would suggest using the next version of Litespeed in your case.

    Hope that helps,
    -Ben-
Reply
  • Hello

    I would suggest using the next version of Litepseed (8.7) rather than TOAD for what you are trying to do.

    You are proably using the newest TOAD and not row compression or page compression in your database. But just simply a compressed backup (In this case version of SQL does not matter).
    It was not supported currently because Litespeed compression is the tool we recommend be used to created SQL compressed backups. Please note that Log reader is designed as a part of Litespeed first, but is shared with the TOAD team.

    Aagin I Would suggest using the next version of Litespeed in your case.

    Hope that helps,
    -Ben-
Children
No Data