October 3, 2011 at 1:36 pm
we are planning to break the SQL 2008 R2 cluster so we can add SSAS on the individual nodes. Infact we will have to reinstall the sql server as well.
So before we do the uninstall we will dettach all the databases. We are also planning to script out all the users.
Just wondering if someone has any advice on how to go about this. If I am missing anything from my plan? Also I do have a few jobs that will be deleted in the process. Is there a way to recreate these jobs?
thanks
October 3, 2011 at 3:37 pm
just out of interest, what do you have against a clustered instance of analysis services?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 3, 2011 at 3:59 pm
Perry Whittle (10/3/2011)
just out of interest, what do you have against a clustered instance of analysis services?
I was just thinking this myself..
As for scripting out the logins, you want to save the password hashes and their internal SID otherwise it is harder to fix the logins on the databases later, the loginNAME might be the same but loginNAME is not stored in the usr databases, the SID assigned to that user is, this is true for windows logins as well, however their domain SID is used in their cases.
Also you will want to script out any special permissions for those users, like what server roles are they members of and any other granted permissions at the server level.
You mentioned jobs, just script them out, SSMS will do that..
CEWII
October 3, 2011 at 5:58 pm
an extra clustered ssas would require an extra license. thats what i was told.
October 4, 2011 at 12:12 am
It is true.
If you have a clustered instance of the database engine and analysis services and database engine is active on node a and SSAS on node b then both nodes need to be licenced.
However, this is also true for what you are planning to do, there is no difference!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 4, 2011 at 12:31 pm
sqlstar2011 (10/3/2011)
an extra clustered ssas would require an extra license. thats what i was told.
That depends a lot on the config, but a separated database and SSAS still requires an additional license.
So the better question is, why don't you explain your end goal and we can give guidance for that. Why don't you explain your current config..
CEWII
October 4, 2011 at 12:40 pm
you dont need an extra license if sql db engine and ssas are active on the same node. you can have them in different resource groups.
problem is that you can add ssas to an existing cluster. so thats why we are breaking the cluster and reinstalling sql.
October 4, 2011 at 12:48 pm
You should be able to create it in a new resource group without removing the existing server. I agree you can't add SSAS to the existing group from the install, been there not been able to do that. I can think of some reasons having it in its own resource group is a good thing.
Knowing that this would be how it was I went ahead and installed only the database even though I might need SSAS in the future.
CEWII
October 4, 2011 at 2:58 pm
sqlstar2011 (10/4/2011)
you dont need an extra license if sql db engine and ssas are active on the same node.
that is correct.
sqlstar2011 (10/4/2011)
problem is that you can add ssas to an existing cluster. so thats why we are breaking the cluster and reinstalling sql.
are you saying you cant add a clustered instance to an existing cluster?
Because you can. Each clustered application will use its own resource group, this is by design.
You don't need to break the cluster!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 4, 2011 at 4:30 pm
From technical view point ,I totally agree with you to discriminate between Clustered SQL Service + AS service in cluster resources.
Thus now, you have to follow up basically the next steps:
1.Create another new group like “Group2” with 3 different SAN LUNS at least other than those of the first Group of SQL Service
2.Assure those 3 SAN LUNs are configured with the best practices ( essentially to be in isolated RAID groups + RAID 5 for 2 SAN LUNs + RAID 1/0 for that specified for log file)
3.Start AS cluster installation , follow the steps until reaching to the step of selecting cluster group , then select Group2
4.Assure relevant APP servers have access to 2383 TCP port with this new cluster
[font="Arial Black"]Performance Guard[/font]
[font="Courier New"]Just ask me to get 0 sec for all queries[/font]
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply