William -
Thanks for your answer. I went looking for a more extensive
explanation and found the following and of course a lot more.
See: http://www.vb-world.net/databases/sqltutorial2/index3.html
http://www.orafaq.com/msgboard/test/messages/41.htm
Clustered � This type of index sorts the entire table based on one or more
indexed fields. Imagine it as a phone book; it organises the Surname field
in ascending order and can therefore find rows quicker based on that field.
Of course, if it were just to search through a random list of data, it would
be much slower. Note though, you can only have one clustered index per table
Non-Clustered � Let's say you add this index to the Surname field. This
index stores all of the Surnames in ascending order somewhere else, along
with a pointer to the original row. So when you search for a particular
Surname, it looks it up in the separate list of surnames, finds the pointer
to the actual row, then speedily retrieves it. You can have more than one
non-clustered index per table
>From various sources it seems that a clustered index is an organization
imposed upon the table as it is physically stored together with other
information which governs the structure of the index. The rows in the table
are stored physically in the sort order of the index. A non-clustered index
is what we usually think of when discussing indexes. It is an independent
reference source with pointers to the position of records within the the
table organized by values of the indexed information.
=======================================
At 10:13 AM 10/6/2001 -0700, you wrote:
>The *complete* answer to that question would take too long to type. The
>*general* answer would be that a clustered index is one that determines and
>tracks the physical storage order of data in a table, whereas a nonclustered
>uses pointers as addresses to rows of data. Clustered indexes can guarantee
>that records in the next sequential order of the index are physically
>located next to the previous record on the disk/data page.
>
>----- Original Message -----
>From: "Bernie Corrigan" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Saturday, October 06, 2001 3:33 AM
>Subject: RE: RE: Name length limitation - personal correction
>
>
>> Eric -
>> You haven't answered Ben's question: What are
>> clustered/non-clustered indexes as related to RBase and Sql? Or in other
>> words, what is the difference between clustered and non-clustered indexes?
>>
>> Bernie
>> =======================================
>> At 11:02 AM 10/5/2001 -0500, you wrote:
>> >The application sets up the tables it needs inside the database you
>> >specify. In my case, Rbase via Oterro. The commands the application
>> >use specify whether the index is a clustered or a non clustered index.
>> >Rbase considers it an invalid command. This is in addition to the fact
>> >that the application needs column names larger than 18 characters, so it
>> >doesn't matter in the grand scheme of things. It would be nice if the
>> >application let you specify your own table names, but that would require
>> >much more work on their end and I don't blame them.
>> >
>> >> -----Original Message-----
>> >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>> >On
>> >> Behalf Of Ben Petersen
>> >> Sent: Friday, October 05, 2001 2:54 AM
>> >> To: [EMAIL PROTECTED]
>> >> Subject: RE: RE: Name length limitation - personal correction
>> >>
>> >> Eric,
>> >>
>> >> What are clustered/non-clustered indexes as related to RBase and
>> >> Sql?
>> >>
>> >> Ben Petersen
>> >>
>> >>
>> >>
>> >> On 4 Oct 2001, at 14:19, Crued @ Crued.net wrote:
>> >>
>> >> > It's not the VarChar that prevents the creation of the tables, it's
>> >that
>> >> > it uses CLUSTERED and NONCLUSTERED Indexes. Having so many problems
>> >> > getting this working that I failed to think about what the problem
>> >> > really was.
>> >> >
>> >> > I think this means I owe someone a quarter, or a pair of socks or
>> >> > something, but I'm not sure how that works. :)
>> >> >
>> >> > Eric
>> >> >
>> >> >
>> >> >
>> >> > >I find it extremely frustrating and downright lame that Rbase only
>> >> > allows >18 char column and table names. In addition to that
>> >horrible
>> >> > limitation, I >found another. Rbase doesn't use standard SQL
>> >datatypes,
>> >> > so the automatic >table creation from the Fax application does not
>> >work.
>> >> > Where it would say >MyKey VARCHAR(19), Rbase wants MyKey TEXT 19.
>> >> > Lameola.
>> >> >
>> >> >
>> >> > > -----Original Message-----
>> >> > > From: [EMAIL PROTECTED]
>> >[mailto:[EMAIL PROTECTED]]
>> >> > On
>> >> > > Behalf Of Albert Berry
>> >> > > Sent: Thursday, October 04, 2001 1:28 PM
>> >> > > To: [EMAIL PROTECTED]
>> >> > > Subject: RE: RE: Name length limitation
>> >> > >
>> >> > > I was asking if the fax program itself had a db, in which you
>> >could
>> >> > create
>> >> > > a view - but it looks like that is not what happens at all. In
>> >this
>> >> > case,
>> >> > > your best bet might be to create a M$ acce$$ db to receive the SQL
>> >> > > statements and SATTACH the acce$$ db to the R:Base db.
>> >> > >
>> >> > >
>> >> > > "Crued @ Crued.net" <[EMAIL PROTECTED]> wrote:
>> >> > >
>> >> > > >The fax program's source database would be our Rbase database. I
>> >> > could
>> >> > > >create a view inside the Rbase DB, but I'm not sure what you are
>> >> > getting
>> >> > > >at doing with it. Due to the fact that the Fax application
>> >issues
>> >> > > >direct SQL to the ODBC driver, I don't think wrapper views would
>> >> > work.
>> >> > > >If you are thinking of some other solution, please let me know as
>> >I'm
>> >> > > >screwed otherwise.
>> >> > > >
>> >> > > >Thanks,
>> >> > > >Eric
>> >> > > >
>> >> > > >
>> >> > > >> -----Original Message-----
>> >> > > >> From: [EMAIL PROTECTED]
>> >> > [mailto:[EMAIL PROTECTED]]
>> >> > > >On
>> >> > > >> Behalf Of Albert Berry
>> >> > > >> Sent: Thursday, October 04, 2001 12:28 PM
>> >> > > >> To: [EMAIL PROTECTED]
>> >> > > >> Subject: RE: Name length limitation
>> >> > > >>
>> >> > > >> Can you create a view in the fax program source database that
>> >> > renames
>> >> > > >the
>> >> > > >> fields to 18 characters or less?
>> >> > > >>
>> >> > > >>
>> >> > > >>
>> >> > > >> "Crued @ Crued.net" <[EMAIL PROTECTED]> wrote:
>> >> > > >>
>> >> > > >> >Our Fax program can use an ODBC source for archival purposes.
>> >The
>> >> > > >> >tables that it uses are hard coded into their program, and
>> >some of
>> >> > > >the
>> >> > > >> >field names are longer than 18 characters.
>> >> > > >> >
>> >> > > >> >Is there anyway around this?
>> >> > > >> >
>> >> > > >> >Thanks,
>> >> > > >> >Eric
>> >> > > >> >
>> >> > > >> >
>> >> > > >> >
>> >> > > >>
>> >> > > >>
>> >> > > >>
>> >__________________________________________________________________
>> >> > > >> Your favorite stores, helpful shopping tools and great gift
>> >ideas.
>> >> > > >> Experience the convenience of buying online with Shop@Netscape!
>> >> > > >> http://shopnow.netscape.com/
>> >> > > >>
>> >> > > >> Get your own FREE, personal Netscape Mail account today at
>> >> > > >> http://webmail.netscape.com/
>> >> > > >
>> >> > > >
>> >> > >
>> >> > >
>> >> > > __________________________________________________________________
>> >> > > Your favorite stores, helpful shopping tools and great gift ideas.
>> >> > > Experience the convenience of buying online with Shop@Netscape!
>> >> > > http://shopnow.netscape.com/
>> >> > >
>> >> > > Get your own FREE, personal Netscape Mail account today at
>> >> > > http://webmail.netscape.com/
>> >> >
>> >> >
>> >
>> >
>>
>>
>
>
