The forum will experience an outage sometime between February 10 at 7:00pm EST and February 12 at 11:59 EST for installation of security updates. The actual time and duration of the outage are unknown but attempts will be made to minimize the downtime. We apologize for any inconvenience.

I think the answer is "no"... here's the situation: An application based on SQL Anywhere web services currently uses unfriendly names for the web services...

CREATE SERVICE unfriendly ... AS CALL whatever ( ... );

CREATE PROCEDURE whatever ( ... ) ...

and the wish is to present more friendly service names to the web browser, implementing the change over time without immediately disabling the old names, so duplicate service definitions are proposed...

CREATE SERVICE unfriendly ... AS CALL whatever ( ... );

CREATE SERVICE friendly ... AS CALL whatever ( ... );

CREATE PROCEDURE whatever ( ... ) ...

Considering that the rate of service invocations will not change, and that each invocation will use either the old name or the new name, will there be a performance penalty other than the miniscule overhead for more stuff in the system catalog?

asked 22 Jul '12, 06:43

Breck%20Carter's gravatar image

Breck Carter
accept rate: 21%

edited 23 Jul '12, 11:03

Mark%20Culp's gravatar image

Mark Culp

Breck: you are correct. There will be a small but negligible performance penalty to have the additional entry in the syswebservice table (and hence another entry to find or skip over when matching the URL to the web service), but beyond that there will be no effect.

Calling the same procedure from different web services is not a factor what-so-ever. Note: Within the procedure you can use http_variable('@HttpURI') to get the URL that was used to access the web service (in case you want to determine if anyone is using the old 'unfriendly' service).

permanent link

answered 23 Jul '12, 09:58

Mark%20Culp's gravatar image

Mark Culp
accept rate: 40%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • 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: 22 Jul '12, 06:43

question was seen: 583 times

last updated: 23 Jul '12, 11:03