April 24, 2006 at 9:50 am
We are working on our first DW in sql 2000 (later sql2005). We anticipate loading 30GB+ of data into our Analysis server. Is it possible to increate the sql page size from 8K to something larger? (I'm hoping that doing so would facilitate the data loading speed. Or would that just cause more trouble down he line?)
Bill
April 24, 2006 at 5:25 pm
I don't believe that you can increase the page size in SQL but I'm not sure you'd need to either. Is your concern around the SQL performance or the AS performance?
With both (SQL and AS) if you're working with large data sets you should really be considering partitions. e.g partition your cube by year, so you can process only the current years partition daily and maybe reprocess the previous years each weekend or month, depending on how much your history changes. You could (should) also use partitioned views on the SQL side where you have many physical tables (again, say one for each years worth of data) that appear to be a single physcical object to client apps via a view, this can let you distribute just on the one server (local partitioned views) or across many (distributed partitioned views).
Steve.
April 25, 2006 at 6:33 am
Just as an FYI, we were told by Scalability Experts to skip AS 2000 and go to AS 2005 due to the amount of changes. I have also attended some MS sponsored hands on training sessions in which the instructor, per MS, suggested recreating any cubes you have in AS 2000 from scratch for AS 2005.
April 25, 2006 at 8:53 am
Absolutely, if you have a choice definitely go for AS & SQL 2005. The ProClarity doco on migrating from 2k to 2k5 also recommends doing a complete rebuild.
Steve.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply