Re: Oracle v/s SqlServer ...

  • From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Thu, 3 Jun 2004 14:11:15 +0100

The answer is yes and sort of. 

IOT
===
Rather surprisngly to anyone from an oracle background *most* tables
in an MSSQL database will be stored in a specific index order. The
concept to look for in books online is Clustered Index. The index
doesn't have to be the primary key for the table, and indeed it may
well make sense for it not to be. There is no overflow segment either.
How do you use them - simply create a clustered index on the table.

Partitioning
========
What you get are partitioned views, that is to say you effectively get
a table for each partition and then a union all view of all
partitions. The partition key must be NOT NULL - makes sense - and
mssql applies a CHECK constraint to the partitioning key. The table
must have a primary key which includes the partition key. As of
MSSQL2k you can do this across different databases - then it gets
called Distributed Partition Views if you have any sense of Federated
Databases if you are in marketing :)

Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.com



----- Original Message -----
From: Harsh Agrawal <harsha@xxxxxxxxxx>
Date: Thu, 3 Jun 2004 14:05:54 +0300
Subject: Oracle v/s SqlServer ... 
To: oracle-l@xxxxxxxxxxxxx














Hi Xperts,




Below is the question related to Oracle & SqlServer. 




Do we have "Index Organized Tables" and "Partioned Tables" in SqlServer 2k ?




How do we use them in SqlServer2k ? 




__________________________

Thanks and Regards,

Harsh Agrawal
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Other related posts: