locked
Recommendations for Deployment of BI in Existing Farm SP 2013 RRS feed

  • Question

  • We are already have SharePoint Farm 2013 running with SP Applications, now we are planning to deploy BI Application and feature.  What is the recommendation in this scenario, do we need to consider existing SP 2013 farm or should have dedicated farm for BI? Please help me.

    I don’t find any document specifically that talks about this situation.


    Thanks, Ram Ch


    Tuesday, April 1, 2014 7:27 AM

Answers

  • Depending on your BI application you need to take decision.

    As this is more from BI side you need to plan more from SQL server side rather then SharePoint. If the SQL server can take load for BI application and sharepoint can equally support with same hardware, you can go for same farm or IF BI is consuming tooo much resources then plan for new farm.

    • Marked as answer by star.wars Monday, April 14, 2014 1:30 AM
    Tuesday, April 1, 2014 9:36 AM
  • Hiya,

    there are really two considerations here:

    1: as Inderjeet Singh Jaggi states; Ressources. Can your current farm support both. As SharePoint 2013 scales out, you should be able to keep the same farm, just scaling out as required. Secondly, depending on your BI implementation, there might be a large load on the SQL server associated. This SQL does not need to be within the SharePoint farm. So that can be handled separately.

    2: Authentication; Depending on your BI implementation, you might need a specific authentication model. (Kerberos, EffectiveUserName or SecureStore). Your existing implementation might be able to handle this, or there might be special considerations.

    Bottomline - There is no direct technical nor practical reason not to place your BI implementation on the same farm as your exiting SharePoint Applications. There are a few considerations, but nothing magical :)

    • Marked as answer by star.wars Monday, April 14, 2014 1:30 AM
    Tuesday, April 1, 2014 10:54 AM

All replies

  • Depending on your BI application you need to take decision.

    As this is more from BI side you need to plan more from SQL server side rather then SharePoint. If the SQL server can take load for BI application and sharepoint can equally support with same hardware, you can go for same farm or IF BI is consuming tooo much resources then plan for new farm.

    • Marked as answer by star.wars Monday, April 14, 2014 1:30 AM
    Tuesday, April 1, 2014 9:36 AM
  • Hiya,

    there are really two considerations here:

    1: as Inderjeet Singh Jaggi states; Ressources. Can your current farm support both. As SharePoint 2013 scales out, you should be able to keep the same farm, just scaling out as required. Secondly, depending on your BI implementation, there might be a large load on the SQL server associated. This SQL does not need to be within the SharePoint farm. So that can be handled separately.

    2: Authentication; Depending on your BI implementation, you might need a specific authentication model. (Kerberos, EffectiveUserName or SecureStore). Your existing implementation might be able to handle this, or there might be special considerations.

    Bottomline - There is no direct technical nor practical reason not to place your BI implementation on the same farm as your exiting SharePoint Applications. There are a few considerations, but nothing magical :)

    • Marked as answer by star.wars Monday, April 14, 2014 1:30 AM
    Tuesday, April 1, 2014 10:54 AM
  • Hi Ram,

    As Inderjeet states "Depends on your BI application you need to take decision" and also need to consider your hardware,storage and network capacity, software licensing before taking decision.

    If the load of BI application is less (considering near future) then prefer to go with existing farm otherwise you can go with dedicated farm.

    Regards,

    Senthil


    • Edited by SenthilSK Tuesday, April 1, 2014 12:42 PM
    Tuesday, April 1, 2014 12:42 PM