|
Internal database client packet-level replay tools do exist in technical support. However, we do not publicly distribute these tools with SQL Anywhere - they are generally for internal use (or would be provided directly to customers via a technical support case). Externally, we expect these tools to be used for diagnostic purposes only, in scenarios where the interaction between the database server and database client isn't fully understood and we are trying to capture the client-level protocol behaviour for later analysis. May I ask what the background is for this question? Is this intended for a performance test? If you are trying to create a performance test, you may want to take Volker's advice but modified slightly: you will likely also want to consider all requests to the database server (including SELECTS), so relying on just the transaction log will miss out on any operations that do not change data. You should run a request-level log capture ( Thank you. This is a very interesting and important tool.
(11 Feb '13, 09:45)
Ilia63
|
|
What about translating the transaction log with DBTRAN (possibly for a certain log offset range and including/excluding particular users) and run the generated SQL against a backup of the database that does not already contain these operations? I.e. in a very simple scenario:
Thank you for Your reply. But I would like to have a tool, for example, to test the patches. Suppose I need to test the new patch (EBF). I keep a copy of the production database (= backup of the database), delete the log-file and start production database to capture the workload. Running the dbtran for the new log-file (for example, dbtran -a -t db.log db.sql). Then I apply a new patch to the backup of the database. Can I apply this script to verify of the patched database? Let I get the script for each user (for example, dbtran.exe -a -t -u "surg01" db.log db_surg01.sql, ...). Can I use them to test the performance change or deadlocks for patched database? In my opinion, to test the patched database, we should apply the script is not for every user, but for each connect. And we must do it in sync. Can I do this using a SQL Anywhere or SQL Anywhere - utility?
(11 Feb '13, 09:35)
Ilia63
|
