> From: "Daniel Alvarez" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Subject: unsubscribe
> Date: Fri, 10 Jan 2003 20:13:57 +0100
>
>> Date: Fri, 10 Jan 2003 15:33:49 -0400
> Organization: Mega Soft Computacio, C.A.
>
> Hi, I am a former MS-SQLServer user. When using SQLServer, I used to have
> multiple databases hosted by a single database server, which is represented
> as a single system service.
>
> In SAPDB, each database is a service, so I wonder how should I parcel my
> sets of tables (schemas), since I no longer have the database concept in the
> way that SQLServer uses it. I know that SAPDB 7.4 does not have schemas
> (right?), and I read somewhere in the SAPDB docs that it is not recommended
> to have more than one database instance per server, so my question is:
> Should I use the User as the schema equivalent, and create tables for
> different businesses using a different user for each "business". I want to
> use a single database instance to store tables for different (and unrelated)
> applications, but I don't have a clear picture about how to create a
> boundary between these tables.
>
> Any help will be very appreciated and IMHO, such material should be a part
> of the "SAPDB database concepts" section in the docs. It's kind of difficult
> for an open source project to attract new users without more user friendly
> docs, I suspect that many new users will come from the
> MS-Access/MS-SQLServer world.
Not just the Sybase and MS world. Those of us from an orthodox Unix -
Informix
background also struggle with the absence of a database concept in
SAPDB.
What SAPDB calls a database, Informix calls a server instance. Informix
allows
as many databases as you like in an instance, and as many instances as
you
like on a server (although, to be fair, they now discourage you from
have
multiple instances on a server)
I feel that there is a need for an internediate layer of documentation
giving an overview of the SAPDB architecture with emphasis on how this
contrasts with the other currently more familiar setups (Informix,
Sybase,
Oracle, Postgres, etc).
Why is there no demo database (in the Informix sense) created at setup
time?
We get an instance but with no data in it to play with? I spent 7 days
modifying the Informix stores demo database so that it could be uploaded
into a SAPDB instance. In the process, I had to plough through hundreds
of pages of replcli documentation to find out how to do so. (I still
cannot
load the dates properly without using a perl script to modify the load
files
first). One or 2 pages of examples would have been sufficient.
The current documents are good and complete but labyrinthine and
tediously
slow to plough through when you are looking to find things like:
1. Is there a PREPARE statement? (Yes)
2. How do you do outer joins (ANSI SQL92 style or Oracle or whatever)?
(SQL92)
3. Is there an INTERVAL data type. (Seemingly No )
4. How do your load Dates into a database and translate from D/M/YYYY
say? (Dunno)
5. How do you include the return value of a stored procedure in an SQL
query
(I suspect that you cannot).
6. How do you get Unix ODBC to work for an ordinary user? (The howtos
do not work for me)
I long for a more conpressed, compact style which I can search quickly,
rather
than the 7 words per HTML page style, 5 levels deep which prevails now.
My feeling is that SAPDB is probably a very good (or nearly so) database
engine
but it is damned difficult to get started on (compared with Informix,
Sybase, Postgres,
etc).
John O'Gorman
>
> Regards,
> [EMAIL PROTECTED]
>
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
