vendor announcement: SQLA to move to Sybase.com

[Chris_Kleisath]

In light of the impending demise of the SQLA site on stackexchange.com, we intend to migrate the existing SQLA site to a site to be hosted on Sybase.com.

We hope to complete the migration in the next few weeks. We will announce the new site's availability through our varied support channels, including blogs, nntp newsgroups, etc.

[VolkerBarth]

Great news - as long as its still a website and not NNTP 🙂

[Chris_Kleisath]

Yes, the Sybase hosted site will be a website, and not NNTP.

[MCMartin]

Glad to hear this!

[former_SQLA_member1694886]

Are you going to be using OSQA with SQL Anywhere as a back-end?

[Former Member]

REALLY GLAD to hear Sybase is on-board with keeping this going. Thanks to our friends and supporters at iAnywhere!

[Chris_Kleisath]

@Vincent Buck: Once we get the new site up and running, we will describe exactly what we did. Until then, I hesitate to say exactly what we are doing because some things could change before launch. We did start with the OSQA open source though. Clearly, we won't host something ourselves that doesn't use SQL Anywhere!

[Former Member]

This is fantastic! Another reason why SQLAnywhere rocks!

[VolkerBarth]

@Chris: If you do port something like OSQA or another open source system to SQL Anywhere - would you share that for other uses (e.g. in a manner Jason Hinsperger shared his Wordpress/SA adaptions in his blog, cf. http://iablog.sybase.com/hinsperg/2008/04/setting-up-a-blog-server)? - I do know it's too early to ask but that could be even more advantageous:)

[MarkCulp]

@Volker: FWIW as part of our investigations we were able to get OSQA to run on SQL Anywhere with no effort at all - you just need to install the SQL Anywhere django and python drivers and viola, it just worked! 🙂

[MarkCulp]

*IMPORTANT NOTE TO ALL USERS Please ensure that your SQLA user profile contains a valid email address - when the site gets moved, in order for you to keep your same user name (and its associated badges, tags, points, etc) you will need to reauthenticate your account and this will most likely (i.e. we're still testing) be done by an email being sent to your email address that exists in your profile.

[MarkCulp]

BTW to check that your email address is correct, login, click on your name at the top of the page, then click the "edit" link beside the "Registered User" header. Your current profile personal data will be then displayed and made editable. Update your email address if it is blank or incorrect and then click "Save Profile".

[Chris_Kleisath]

@Volker: In this whole process, we DO hope to create a blog post or two that describes what we did, but as Mark said, for the most part it "just worked!" using SQL Anywhere version 12.

[VolkerBarth]

@Mark, @Chris: It was worthwhile to introduce the LIMIT clause in V12, I guess:)

[MarkCulp]

@Volker: The SQL Anywhere django and python driver was released with 11.0.x. Support for the LIMIT clause is not a prerequisite for OSQA to work.... the django driver does all of the right stuff to make everything just work.

[Breck_Carter]

To all: Please send an email to rcartaino@stackoverflow.com asking him to extend the life of sqla.stackexchange.com from July 13 (the current end-of-life) by two weeks.

[Former Member]

Done. Just sent an email.