Dear Professional.

I would appreciate if you can guide me one thing. I am working on one of the
trading environment and I am expecting billions of records in order table. I
am thinking to move historical record into Historical Database and fetch the
record from Historical database if needed and implement the Partition on top
of it which Partitioning I have to implement Data Range or ??.

I am not sure this is the right solution or I have to adopt different
approach.

Please advice.

Thanks

Yes, you can create a horizontal partion on the table.

create a view on the base table and the archive table with union all.
create a check constraint on the archive table to enter the data below the
specific date. this will redirects your query from the view to searcht the
historical table only , instead of the base table.





"Noor" wrote:

Yes, you can create a horizontal partion on the table.

create a view on the base table and the archive table with union all.
create a check constraint on the archive table to enter the data below the
specific date. this will redirects your query from the view to searcht the
historical table only , instead of the base table.





"Noor" wrote:

Yes, you can create a horizontal partion on the table.

create a view on the base table and the archive table with union all.
create a check constraint on the archive table to enter the data below the
specific date. this will redirects your query from the view to searcht the
historical table only , instead of the base table.





"Noor" wrote:

Yes, you can create a horizontal partion on the table.

create a view on the base table and the archive table with union all.
create a check constraint on the archive table to enter the data below the
specific date. this will redirects your query from the view to searcht the
historical table only , instead of the base table.





"Noor" wrote:

Yes, you can create a horizontal partion on the table.

create a view on the base table and the archive table with union all.
create a check constraint on the archive table to enter the data below the
specific date. this will redirects your query from the view to searcht the
historical table only , instead of the base table.





"Noor" wrote:

Yes, you can create a horizontal partion on the table.

create a view on the base table and the archive table with union all.
create a check constraint on the archive table to enter the data below the
specific date. this will redirects your query from the view to searcht the
historical table only , instead of the base table.





"Noor" wrote:

Yes, you can create a horizontal partion on the table.

create a view on the base table and the archive table with union all.
create a check constraint on the archive table to enter the data below the
specific date. this will redirects your query from the view to searcht the
historical table only , instead of the base table.





"Noor" wrote:

Yes, you can create a horizontal partion on the table.

create a view on the base table and the archive table with union all.
create a check constraint on the archive table to enter the data below the
specific date. this will redirects your query from the view to searcht the
historical table only , instead of the base table.





"Noor" wrote:

Yes, you can create a horizontal partion on the table.

create a view on the base table and the archive table with union all.
create a check constraint on the archive table to enter the data below the
specific date. this will redirects your query from the view to searcht the
historical table only , instead of the base table.





"Noor" wrote: