vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| SQL 2K I am creating a table for holding data used for data wear-housing project. This table will eventually going to have millions of records. Planned to have a primary key and proper indexing in this table. This table will be queried against various columns and will be refreshed (fill data) on a weekly basis. Is there any other approach I should think about like - Partitioned views or ?? Any thoughts/Ideas will be highly appreciated. Thanks Sh |
| ||||
| First of all, consider using Analysis Services for querying. Check the "Data Warehousing and OLAP" module in Books OnLine (mk:@MSITStore:C:\Program%20Files\Microsoft%20SQL% 20Server\80\Tools\Books\ol apdmad.chm::/agaboutolap_9i5s.htm). -- Dejan Sarka, SQL Server MVP FAQ from Neil & others at: http://www.sqlserverfaq.com Please reply only to the newsgroups. PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Shamim" <shamim.abdul@railamerica.com> wrote in message news:eml2mZLQDHA.2316@TK2MSFTNGP11.phx.gbl... > SQL 2K > > I am creating a table for holding data used for data wear-housing project. > This table will eventually going to have millions of records. > Planned to have a primary key and proper indexing in this table. > This table will be queried against various columns and will be refreshed > (fill data) on a weekly basis. > > Is there any other approach I should think about like - Partitioned views or > ?? > > Any thoughts/Ideas will be highly appreciated. > > Thanks > Sh > > |