Re: Where is the newsgroup for SQL Anywhere ?

Kyte,

Why do you insist on posting erroneous information about Sybase's products even after you've been told that it's erroneous?

Francisco

In <4a5m56$at2_at_inet-nntp-gw-1.us.oracle.com> tkyte_at_us.oracle.com (Thomas J Kyte) writes:
>
>fcasas_at_ix.netcom.com (Francisco Casas) wrote:
>
>Casas (since we appear to be on a last name basis)
>
>>Kyte,
 

>>Since when have you (an Oracle employee) become the authority on
>>Sybase products? Let me correct your misrepresentations of the
 facts.
>>Look for the ## marks.
>
>Read below Francisco, I pretty PLAINLY SAID "Is PC Magazine
 incorrect". I was
>simply QUOTING an article that just evaluated Sql anywhere, Personal
 Oracle and
>Gupta SQLBase. Never claimed to be an expert on Sql Anywhere, sort of
 asked
>questions. I think you take this way too personal.
>
>>Francisco
 

>>In <49vbds$eq1_at_inet-nntp-gw-1.us.oracle.com> tkyte_at_us.oracle.com
>>(Thomas J Kyte) writes:
>>>
>>>fcasas_at_ix.netcom.com (Francisco Casas) wrote:
>>>
>>>>Hi Sam,
 

>>>>You are correct. SQL Anywhere is 100% compatible with T-SQL and
>>>>Open Client. SQL Anywhere is targeted for single users (a small
>>>>footprint 1-2MB of RAM and ~10MB of disk) on MS-Windows. The NT
>>>>version targeted for the workgroup market (20 concurrent users
>>>>or there about), while SQL Server 11 is targeted at heavier loads.
 

>>>>Francisco
>>>
>>>Is PC magazine incorrect then when the December 19'th issue states
>>>that it needs 8meg of ram and 20mb of disk?
>>>
>>##
>>Those estimates are not equivalent to those I've obtained less a few
>>minutes ago when I tested it. It takes about 1MB of RAM and a little
>>less than 10MB for a runtime environment.
>>##
>
>Well, I was just quoting the PC Magazine issue, nothing more, nothing
 less. How
>much ram do you have on your PC. Perhaps they are saying you need an
 8meg
>machine to run on confortably.
>
>>>
>>>To use Open Client don't you also need to use an OpenServer Gateway
 on
>>>the PC (except of course on Windows 95 where this won't be an
 option,
>>##
>>Get a clue! Open Client is the equivalent of your (Oracle)
>>OCI/SQL*Net combination. Open Client does not need an Open Server
>>to communicate to! And unlike your (Oracle) architecture where a
>>SQL*Net is required on both the client and the server, we don't
>>require that our Net-Lib (a component of Open Client) be required
>>at the server at all.
>>##
>
>Simply quoting the PC Magazine article verbaitim. Perhaps you should
 be saying
>"PC Magazine, Get a Clue" (and if so I will look for their retraction
 in the
>next issue). Why would pc magazine say that Sybase SQL Anywhere
 unfortunately
>only supports Open Client via the use of an Open Server (eg: client
 talks to
>open server, open server understands open client, open server
 translates open
>client into watcom api). The article clearly states that the ONLY Api
 to 'SQL
>Anywhere' is ODBC or 4gls like powerbuilder and on Windows 95
 standalone, that
>be it, no openserver to get access. The fully compliant with Open
 Client
>applies only when the SERVER is running on some other platform like
 NT.
>
>As to the sql*net client, sql*net server that is purely a license
 issue. Are
>you telling me that on the server you (Sybase) don't have some piece
 of software
>linked into your server that allows it to talk on the network
 protocol. Gee,
>when I programmed Sybase there was DEC Net supported servers and TCP
 supported
>servers (at least in the environment I was concerned with). Sure did
 seem that
>the server had *something* in it to allow it to talk to a given
 protocol. You
>have the equivalent of sql*net on the server from a technical
 perspective.
>Purely a license thing here, so what. Netlib is on the server from a
 code
>perspective.
>
>>>the PC (except of course on Windows 95 where this won't be an
 option,
>>>no Open Client/dblib access on standalone PC's), wouldn't this as
 well
>>##
>>What are you talking about? There's definately a Win95 version of
>>Open Client and a Win95 version of Open Server is not needed for
 client
>>nodes (your understanding of Open Server is way off - You Sybase
 expert
>>you - AKA Oracle employee).
>>##
>
>I am talking only about SQL Anywhere here. Can you write, on a
 standalone,
>non-networked, laptop running Windows 95 An OPEN Client Application
 that access
>SQL Anywhere? The Pc Magazine article said pretty clealy, NO. I am
 just
>quoting.
>
>>>bump up the requirements? On a standalone Windows95, SQL Anywhere
>>>really only supports ODBC and 4gls like Powerbuilder since the
>>>OpenServer won't run there.
>>##
>>You are wrong again. SQL Anywhere is 100% compliant with Open Client
>>10.x and above. It does support ODBC but it is not required. Get a
>>clue about Open Server!!!!!
>>##
>
>Not according to the review. Maybe they are wrong. Why don't you get
 them to
>print a retraction to clear it up.
>
>>>
>>>[snip]
>>>
>>>Thomas Kyte
>>>tkyte_at_us.oracle.com
>>>Oracle Government
>>>
>
>
>Thomas Kyte
>tkyte_at_us.oracle.com
>Oracle Government
>
Received on Fri Dec 08 1995 - 00:00:00 CET