|
Hi. We have a packingstation with a weight (Windows-based touchscreen) which sends data to a SQL Anywhere 12 database. From time to time the users complain that the process of storing data is slow, and it halts the production. The actual insert-statment is executed in a stored procedure which is called in our software on the weight. The weight and the database is in separate networks (different subnets), but on the same physical network. This is unfortunately how the IT-department wants it. Is there any tool, command or similar available to measure how much time the server uses to complete the task. That being to measure the time it takes from the call to the stored procedure is sent from our software until the row is stored in the database. We would like to prove (hopefully) that our software is not the problem, so the IT-department at our customers location can look into their infrastructure instead. Regards, Bjarne Anker Maritech Systems As Norway |
Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 30 Sep '15, 09:18
question was seen: 2,002 times
last updated: 13 Oct '15, 07:28
No answer - but here's a FAQ dealing with several ways to test a "round trip", so that may or may not be of some help:
What is the quickest statement?
That being said, wouldn't it help to add some logging of the timings of your code around the stored procedure call - or to log on the server side when the procedure gets called and when it does finish the operation? (I'd think something like request level logging would be over-sized (unless you can limit it to the call of that particular procedure) and might slow down the real traffic significantly but you could give that a try, as well.)
I'm sure I remember a Sybase command line utility that allowed you to get very detailed execution times for a statement - it gave a full breakdown of all the individual elements of preparing, executing, returning data etc. I can't remember what it was called - but maybe someone else will.
Do you think of the FETCHTST utility and its variants?
That's the one.