|
Home > Archive > SQL Anywhere database > April 2005 > Does dbunload use ORDER ON?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Does dbunload use ORDER ON?
|
|
| Breck Carter 2005-04-18, 9:23 am |
| Does dbunload use ORDER ON?
Does 9.0.2.3044 dbunload.exe use the UNLOAD TABLE ORDER ON
option when unloading tables via -ii or -ix?
If so, please confirm that the following technique would
work to convert an index to CLUSTERED at the same time as
migrating from version 8 to 9:
(1) Start the ASA 8 database with the ASA 9 server.
(2) Alter the index to be CLUSTERED.
(3) Run the ASA 9 dbunload, dbinit and dbisql reload.sql.
Dbunload will unload the table in the order of the index
marked clustered, and the reload will actually load the rows
in the order of the clustered index.
Breck
| |
| Nick Elson 2005-04-18, 11:23 am |
| AFAIK, dbunload (and unload table) has always used
the Primary Key (and now clustered index if one exists)
from the earliest days.
Further, this behavior has never been tied to the
'internal' (-i* or -*i)
or
'external' (-x* or -*x)
options picked.
Have you noted a behavior where build 3044 behaves
differently? Or did I miss something? [the online doc
does state "With ORDER ON (the default), the exported
data is ordered by clustered index if one exists."]
As to your 1,2,3. That sounds correct to me.
<Breck Carter> wrote in message news:4263bd62.1a1c.1681692777@sybase.com...
> Does dbunload use ORDER ON?
>
> Does 9.0.2.3044 dbunload.exe use the UNLOAD TABLE ORDER ON
> option when unloading tables via -ii or -ix?
>
> If so, please confirm that the following technique would
> work to convert an index to CLUSTERED at the same time as
> migrating from version 8 to 9:
>
> (1) Start the ASA 8 database with the ASA 9 server.
>
> (2) Alter the index to be CLUSTERED.
>
> (3) Run the ASA 9 dbunload, dbinit and dbisql reload.sql.
>
> Dbunload will unload the table in the order of the index
> marked clustered, and the reload will actually load the rows
> in the order of the clustered index.
>
> Breck
| |
| Breck Carter 2005-04-18, 1:23 pm |
| Dbunload is a black box... I was just seeking confirmation
that it didn't use an undesirable override :)
Breck
> AFAIK, dbunload (and unload table) has always used
> the Primary Key (and now clustered index if one exists)
> from the earliest days.
>
> Further, this behavior has never been tied to the
> 'internal' (-i* or -*i)
> or
> 'external' (-x* or -*x)
> options picked.
>
> Have you noted a behavior where build 3044 behaves
> differently? Or did I miss something? [the online doc
> does state "With ORDER ON (the default), the exported
> data is ordered by clustered index if one exists."]
>
> As to your 1,2,3. That sounds correct to me.
>
> <Breck Carter> wrote in message
> dbunload use ORDER ON? >
> reload.sql. >
>
>
| |
| Nick Elson 2005-04-18, 8:23 pm |
| If it helps,
Currently dbunload uses the 'unload table' statement (for -i*)
as well as forms the select for the output operation (for -x*)
[-zr sql will show you all that ... for the -x* you will only see the
select statement but you'll get the point]
<Breck Carter> wrote in message news:4263feef.1d9d.1681692777@sybase.com...[color=darkred]
> Dbunload is a black box... I was just seeking confirmation
> that it didn't use an undesirable override :)
>
> Breck
>
|
|
|
|
|