sql/mx catalog/tables - where are they stored?
mustlearntandem
current node and volume". If I run mxci and create a catalog it is
created and I can use it - but where is it stored and how can I manage
it and the tables registered to it. Go ahead and chuckle but I've
looked all over and can't figure it out and it's driving me nuts!
TIA
gaurav
specified disks.
2. System Catalog <node-name>.CATSYS is located in ZSD0 subvol on a
volume stored (specified at the time of SQL/MX initialization) in
$SYSTEM.ZSQLMX.MXANCHOR file.
3. User schemas are by default created in
<default-guardian-vol>.ZSDnnnnn, where nnnnn is automatically
generated.
User can control these location names by specifying LOCATION clause in
CREATE CATALOG, CREATE SCHEMA, and CREATE TABLE statements.
As far as management is concerned 'mxci' is not the best tool to manage
SQL/MX tables. NSMweb (delivered along with SQL/MX for free) is
currently the only way to manage SQL/MX.
HTH.
- Gaurav
Rob Lesan
wrote:
>1. SQL/MX stores all its tables (including system) in ZSD* subvols on
>specified disks.
>2. System Catalog <node-name>.CATSYS is located in ZSD0 subvol on a
>volume stored (specified at the time of SQL/MX initialization) in
>$SYSTEM.ZSQLMX.MXANCHOR file.
>3. User schemas are by default created in
><default-guardian-vol>.ZSDnnnnn, where nnnnn is automatically
>generated.
>
>User can control these location names by specifying LOCATION clause in
>CREATE CATALOG, CREATE SCHEMA, and CREATE TABLE statements.
>
>As far as management is concerned 'mxci' is not the best tool to manage
>SQL/MX tables. NSMweb (delivered along with SQL/MX for free) is
>currently the only way to manage SQL/MX.
>
>HTH.
>
>- Gaurav
Good luck with NSMweb, this is quite possibly the worst user interface
I have I have worked with. No command line, which means no scripting.
Odd syntax, poor documentation, and SLOW.
BTW, did anyone mention that it only works with a single, older
version of Java? Install the wrong one on your workstation and your
screwed.
I wish you luck. Just one more reason SQL/MX is nowhere near ready
for prime time.
Try one of the minimal web based products for managing
Sybase/Oracle/MySql/Postgres before you give NSMweb a spin, just be
prepared for a major letdown.
mustlearntandem
longer clueless (at least about this!).
John Furlong
<snip>
> Good luck with NSMweb, this is quite possibly the worst user interface
> I have I have worked with. No command line, which means no scripting.
> Odd syntax, poor documentation, and SLOW.
>
> Try one of the minimal web based products for managing
> Sybase/Oracle/MySql/Postgres before you give NSMweb a spin, just be
> prepared for a major letdown.
>
Excuse me for butting in, don't want to be pushy, but thought you might
be interested.
I'm project lead on a third-party product called SQLXPress, which is a
tool for use with SQL/MX. It is in limited availability right now,
should be generally available within a month or two.
Briefly, SQLXPress has a fat Windows client, and NSK-resident
MX-specific components (no ODBC ot other middleware).
It addresses four main areas:
DBA functions (create, alter, drop objects, partition management,
grant/revoke, compare DDL, show DDL etc.)
Data browsing and editing - display and edit tablle data in a
spreadsheet-like grid.
Visual query builder - visually create queries, save as text or view,
display result data, export to PC file or MX table.
Execution plan management, includes history database, comparing plans
reporting, program/module/object relationships.
John Furlong
Merlon Software
Rob Lesan
Sounds like a great product, but I use a Mac...