From: Jon Forrest <nobozo@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: segaloco <segaloco@protonmail.com>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Bell COBOL Environment?
Date: Thu, 13 Jul 2023 14:42:19 -0700 [thread overview]
Message-ID: <0CCC47C3-950F-424B-AF6D-0F0DC08C53E5@gmail.com> (raw)
In-Reply-To: <CAC20D2NH7hGbAOCSvbGRk7N1S87wb-RKx-Sva_NjhadCTt-xNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
You’re thinking of Sybase. That’s where the name “SqlServer” came from. Sybase sold a source code license to Microsoft that included the right to use the name.
(I was a developer at Sybase in the VMS group in the late 1980s and early 1990s)
Jon
Sent from my iPhone
> On Jul 13, 2023, at 1:35 PM, Clem Cole <clemc@ccc.com> wrote:
>
>
> Matt - I never had direct (user) experience with it. Ireleases. Also, I do not remember if LPI-Colbol was attached to a specific DB implementation or not. In those days, there were a number of them besides Ingres - Informix, IBM's DB2, and one that started with an S - which later was sold to Microsoft to become SQL-server to name a few, and that may have been part of it.
[-- Attachment #2: Type: text/html, Size: 1170 bytes --]
next prev parent reply other threads:[~2023-07-13 21:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 19:02 [TUHS] " segaloco via TUHS
2023-07-13 20:34 ` [TUHS] " Clem Cole
2023-07-13 20:50 ` Arrigo Triulzi via TUHS
2023-07-13 21:41 ` Kenneth Goodwin
2023-07-13 23:02 ` Clem Cole
2023-07-13 23:19 ` KenUnix
2023-07-13 21:42 ` Jon Forrest [this message]
2023-07-13 22:35 ` segaloco via TUHS
2023-07-13 23:20 ` Warner Losh
2023-07-14 0:20 ` Bakul Shah
2023-07-14 1:16 ` Alan D. Salewski
2023-07-14 1:05 ` David Arnold
2023-07-14 1:45 ` Clem Cole
2023-07-14 2:14 ` Dan Cross
2023-07-14 8:46 Paul Ruizendaal via TUHS
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0CCC47C3-950F-424B-AF6D-0F0DC08C53E5@gmail.com \
--to=nobozo@gmail.com \
--cc=clemc@ccc.com \
--cc=segaloco@protonmail.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).