January 12, 2009 at 7:24 am
I'd like to upgrade my databases from SSAS 2005 to SSAS 2008 to take advantage of all the new features in particular the bugfix for SSAS Backup Time.
After reading the Upgrade WhitePaper
it Suggests that the best and supported way to upgrade is to do an Inplace upgrade. What is unclear to me is is whether a clean Installation of SSAS 2008 on new hardware is a viable and supported option for Migrating to 2008.
I have tested this option after running the Upgrade Advisor against my 2005 server to make sure there are no known feature usage issues then took a backup to an .abf file and restored that on the 2008 test server.
After doing that I was able to browse and process the database, cubes, dimensions etc.
Is there anything nasty about doing the upgrade this way?
January 13, 2009 at 7:07 am
You can upgrade that way if you want to.
I would recommend using BIDS 2008 to upgrade your project, deploying to the 2008 server and doing a full proces of all of your cubes.
January 14, 2009 at 3:40 am
Michael Earl (1/13/2009)
You can upgrade that way if you want to.I would recommend using BIDS 2008 to upgrade your project, deploying to the 2008 server and doing a full proces of all of your cubes.
Any Reason you would do it this way and not just the Backup/Restore?
January 14, 2009 at 4:45 am
The new tool set is better. Upgrading the project and re-deploying and processing will give you an opportunity to look carefully at the cubes and make any necessary adjustments. It will also ensure that your upgraded project in source control (you do have that, right?) will be the same deployed version on your server.
None of these are great reasons, so you could go either way.
November 18, 2009 at 9:50 am
Have you had any issues with aggregations taking exponentially longer after upgrading a cube from 2005 to 2008. I am and can't figure out why.
November 18, 2009 at 3:10 pm
I wouldn't say that they were taking exponentially longer to process.
But something we did find out was that any custom aggregations are not migrated when you move to SSAS 2008.
Only aggs generated by the "Storage Design Wizard" will move across.
As per MSDN article
http://msdn.microsoft.com/en-us/library/ms143742.aspx
Redesign the Custom Aggregations and this fixes the issue of them dissappearing and slowing your user queries.
As for them taking exponentially longer, I'm guessing you mean to build, during processing.
One trick i found is to check that you only have only the aggregations you need and that your attribute hierarchies make sense.
There is some good information out there on this. one of my personal favourites is by Chris Webb.
http://www.sqlpass.ch/LinkClick.aspx?fileticket=6%2bx%2f39vAjJ8%3d&tabid=57&mid=383
Might I suggest reading the SQL Server 2008 White Paper: Analysis Services Performance Guide.
hth
M.
November 20, 2009 at 1:26 pm
So what I'm struggling with is I have a server dedicated to processing cubes (only MSAS 2008 installed) with all kinds of resources in procs and memory and I can't get MSAS to use it. I have read every performance guide out there and read more than 50 blogs posts on this topic.
ServerSpecs:
64GB of Ram never more than 20 is ever allocated or used.
16 Procs Xeon
MSAS 2008 (64Bit)
Windows 2003 Ent (64-bit)
Sometimes the procs will go up to close to 80% usage but mostly idle around 18%. I'm sitting here watching it process cubes asking it to use more of what I'm giving it but can't find the right combination of settings to get it to use more.
As for MSAS config the 2 settings I have been changing are:
CoordinatorExecutionMode = 0 had it at -4 and changed to 0 don't seem to have an effect
ThreadPool\Process\MaxThreas =820 I simply keep doubling this number and it doesn't seem to have much affect.
Any help is appreciated.
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply