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.

alt text

asked 24 Jun '11, 15:55

Breck%20Carter's gravatar image

Breck Carter
accept rate: 20%

edited 24 Jun '11, 16:05

SQL Anywhere - The Shining Edition

permanent link

answered 27 Jun '11, 03:30

Uberseehandel's gravatar image

accept rate: 0%

I like it!

(27 Jun '11, 13:00) Breck Carter

I believe I can pretty much guarantee that the next release of SQL Anywhere will not be called "SQL Anywhere 13".

However, I am not aware of any decisions regarding naming at this time. You'll just have to be patient.

permanent link

answered 24 Jun '11, 17:01

Glenn%20Paulley's gravatar image

Glenn Paulley
accept rate: 43%

What's the reason behind that - does "13" imply too much notion of "bad luck" in some cultures (as does "14" in others)?

If so, well, to me a number is just a number...

Besides that, we will be glad if the product name itself will remain the same:)

(24 Jun '11, 17:10) Volker Barth
Replies hidden

Bad luck is why ASE went from version 12 to 15. Of course the name won't be SQL Anywhere 13 or 14. I'm betting on SQL Anywhere 15 because that's the committee safe choice :)

(25 Jun '11, 11:14) Breck Carter

Are engineers less worried about the symbolic meaning of numbers? - I remember AutoCAD (not a niche product) having versions 13 and 14...

(26 Jun '11, 05:43) Volker Barth

I bet nobody said of any buildings that fell down "oh no! We should have waited for AutoCAD 15! It's okay, engineer-who-designed-the-building, the project was doomed from the outset."

On the other hand, if you run into somebody who is superstitious, it might make it harder to sell them something with a 13 (or 14, depending on the culture) in it.

If a number is just a number, perhaps a UUID would be the best way to label the product. Maybe you want some uniform ordering, though.

(27 Jun '11, 10:23) Phil Mitchell

So you say SQL Anywhere might be made responsible for damaged buildings...?

As to the UUID: Please don't - then I prefer gaps in my default autoincrement:)

(27 Jun '11, 10:41) Volker Barth

SQL Anywhere 0x4b67abbe3c9246f883db0ab2d2b78f8b

(27 Jun '11, 13:03) Breck Carter

A famous person once pointed out that version numbers are a marketing decision. Marketing decisions involve politics. Don't try to apply reason and logic to politics. Such an endeavour rarely ends well.

(29 Jun '11, 10:11) Phil Mitchell

So the code names are all associated with going 'downhill' hmmm

(29 Jun '11, 10:57) trexco
1 now I'm a "famous person", when you reference my blog. :-)

It remains true. The version number is a marketing decision. And you are absolutely right. There are many political considerations.

My own personal bet (remember that I am in engineering) is that the number will be 16.

(29 Jun '11, 13:35) Chris Kleisath

SQL Anywhere 0x10

(29 Jun '11, 13:52) Breck Carter

Better the hill, more fast and fun it is going down!

(29 Jun '11, 13:56) PhilippeBert...

So you say even marketing is aware of hexadecimal notation:)

(30 Jun '11, 03:42) Volker Barth

check out their finger count next time you meet them


(30 Jun '11, 07:49) Uberseehandel

By "famous person" I was referring to the host of Family Feud. ;-)

(30 Jun '11, 09:52) Phil Mitchell

If the sample code from that new 12.0.1 feature (related to .NET 4.5) is somewhat telling, than v16 seems reasonable:)

using (SAConnection conn = new SAConnection("DSN=SQL Anywhere 16 Demo"))

(I just came noticed this reading the fresh EBF readme...)

(20 Aug '12, 03:50) Volker Barth
showing 1 of 15 show all flat view

Maybe like Powerbuilder they are jumping from 12 to 15.

permanent link

answered 20 Aug '12, 05:01

StefanZ's gravatar image

accept rate: 0%


Jump they shall, but not to 15... that number has been used by ASE for the past several years... maybe 15 is good enough for PowerBuilder but not SQL Anywhere :)

Volker has seen the Future!

(20 Aug '12, 12:12) Breck Carter
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: 24 Jun '11, 15:55

question was seen: 3,703 times

last updated: 20 Aug '12, 12:12

Related questions