If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > General > Chit Chat > Pleeease...What is the cursor, index, and cluster?with an example

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-27-04, 05:21
Mr_Shihab Mr_Shihab is offline
Registered User
 
Join Date: Apr 2004
Posts: 13
Smile Pleeease...What is the cursor, index, and cluster?with an example

I studied computer sience in the university?
In my study we practice some SQL statements with Oracle, and SQL Server
Also, We studied some database concepts like
But, until now I haven't clear opinion about CLUSTERS, INDEXES, and CURSORS in the database?

Please give an overview about them with small examples to clarify

Thank you very much
Reply With Quote
  #2 (permalink)  
Old 04-28-04, 05:36
hurmavi hurmavi is offline
Registered User
 
Join Date: Jan 2004
Location: Europe, Finland, Helsinki
Posts: 60
CLUSTERS, INDEXES, and CURSORS

Hi!

Some fast ansvers:

CLUSTERS - this depends very much what product you are talking. Usually this has something to do how the data is located on the disk.
INDEXES - THE MOST INPORTANT feature in real life. Is a physical data structure, typically a b-tree. They are invisble to the SQL-queries, but have a tremendous performace issue.
CURSORS - SQL query usually returns many rows. C, COBOL etc. 3GL-languages can read only one row a time. That's why those program languages need to define a cursor, a feature that allows program to read one row in time.

Cheers, Bill
Reply With Quote
  #3 (permalink)  
Old 05-02-04, 18:06
Nocopy Nocopy is offline
Registered User
 
Join Date: May 2004
Location: Redwood Shores, CA
Posts: 68
Quote:
Originally Posted by hurmavi
Hi!

Some fast ansvers:

CLUSTERS - this depends very much what product you are talking. Usually this has something to do how the data is located on the disk.
INDEXES - THE MOST INPORTANT feature in real life. Is a physical data structure, typically a b-tree. They are invisble to the SQL-queries, but have a tremendous performace issue.
CURSORS - SQL query usually returns many rows. C, COBOL etc. 3GL-languages can read only one row a time. That's why those program languages need to define a cursor, a feature that allows program to read one row in time.

Cheers, Bill
Bill, you probably wanted to say that if you DON'T have indexes than you will have a performance issue.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On