Hello, We are trying to trace some unexpected errors in our application/database with RIBO. The problem is that RIBO creates a lot of ".tds" files. How can I force RIBO to generate the data to one file only?
Thanks a lot,
As Mark mentioned, the RIBO tool along with the jConnect driver are both supplied by the ASE team. Having said that, unless you are specifically trying to track down a TDS protocol error, you can probably get away without using RIBO entirely. Starting the server with the -z option will force the server to provide a full TDS trace (across all connections) in the console log. You could therefore use the -z combined with the -o option to get a full TDS trace in one file. Again though, while the console TDS trace is very complete and usable, it might not help if you are specifically trying to track down a TDS protocol error.
answered 20 Nov '12, 11:06