SharePoint 2013 PerformancePoint services & SQL editions?

Hello All,
We have SharePoint 2013 enterprise edition and we wanna configure PerformancePoint services to use some of its functionalities, What edition of SQL server should we have? Is it OK to use standard edition? Anyone has any reliable technical reference
URL to share with me ?

Overview of SQL Server in a SharePoint environment (SharePoint 2013)
Url: https://technet.microsoft.com/en-us/library/ff945791.aspx
"The minimum requirements for a database server in SharePoint 2013 are SQL Server 2008 R2 with Service Pack 1 (SP1) or SQL Server 2012, or SQL Server 2014 64-bit versions. Note that to use the business intelligence (BI) tools in SharePoint Server
2013 you must install SQL Server 2012 with Service Pack 1 (SP1) or SQL Server 2014, 64-bit version"
SharePoint Foundation 2013 does not support BI features, which require SharePoint Server 2013.
Ricardo Lacerda

Similar Messages

  • Can we use SSRS in sharepoint 2013 standard and sql server standard edition

    can we use SSRS in sharepoint 2013 standard and sql server standard edition
    MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

    Yes you can. You do lose some features:
    http://msdn.microsoft.com/en-us/library/cc645993.aspx#Reporting
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Sharepoint 2013 Reporting Services & OLAP Cubes for Data Modeling.

    I've been using PowerPivot & PowerView in Excel 2013 Pro for some time now so am now eager to get set up with Sharepoint 2013 Reporting Services.
    Before set up Reporting Services  I have just one question to resolve.
    What are the benefits/differences of using a normal flat table set up, compared to an OLAP cube?
    Should I base my Data Model on an OLAP Cube or just Connect to tables in my SQL 2012 database?
    I realize that OLAP Cubes aggregate data making it faster to return results, but am unclear if this is needed with Data Modeling for Sharepoint 2013.
    Many thanks,
    Mike

    So yes, PV is an in-memory cube. When data is loaded from the data source, it's cached in memory, and stored (compressed) in the Excel file. (also, same concept for SSAS Tabular mode... loads from source, cached in mem, but also stored (compressed) in data
    files, in the event that the server reboots, or something similar).
    As far as performance, tabular uses memory, but has a shorter load process (no ETL, no cube processing)... OLAP/MDX uses less memory, by requiring ETL and cube processing... technically tabular uses column compression, so the memory consumption will be based
    on the type of data (numeric data is GREAT, text not as much)... but the decision to use OLAP (MDX)/TAB (DAX) is just dependent on the type of load and your needs... both platforms CAN do realtime queries (ROLAP in multidimensional, or DirectQuery for tabular),
    or can use their processed/in-memory cache (MOLAP in multidimensional, xVelocity for tabular) to process queries.
    if you have a cube, there's no need to reinvent the wheel (especially since there's no way to convert/import the BIDS/SSDT project from MDX to DAX). If you have SSAS 2012 SP1 CU4 or later, you can connect PV (from Excel OR from within SP) directly to the
    MDX cube.
    Generally, the benefit of PP is for the power users who can build models quickly and easily (without needing to talk to the BI dept)... SharePoint lets those people share the reports with a team... if it's worthy of including in an enterprise warehouse,
    it gets handed off to the BI folks who vet the process and calculations... but by that time, the business has received value from the self-service (Excel) and team (SharePoint) analytics... and the BI team has less effort since the PP model includes data sources
    and calculations - aside from verifying the sources and calculations, BI can just port the effort into the existing enterprise ETL / warehouse / cubes / reports... shorter dev cycle.
    I'll be speaking on this very topic (done so several times already) this weekend in Chicago at SharePoint Saturday!
    http://www.spschicagosuburbs.com/Pages/Sessions.aspx
    Scott Brickey
    MCTS, MCPD, MCITP
    www.sbrickey.com
    Strategic Data Systems - for all your SharePoint needs

  • Do we require to install microsoft excel in sharepoint 2013 server?. if require to use sharepoint 2013 excel services.

    Do we require to install microsoft excel in sharepoint 2013 server?. if require to use sharepoint 2013 excel services.
    In our organisation, development team is asking to install office 2013 in SharePoint 2013 server to use different services, where as architecture team not allowing for the same. I need to provide proper justification for installing office 2013 in SharePoint
    2013 server. Please provide me the correct solution for the same.

    No, you do not need to install Office on the SharePoint server to utilize the Excel Services. Office should not be installed on the SharePoint server.
    Do they need Office Web Apps? Are they looking to have the capability to edit documents in the browser maybe? Or have document preview on search? Office Web Apps would be required for this, but this is a different product than Office.
    Brandon Atkinson
    Blog: http://sharepointbrandon.com

  • Using Excel 2010 with SharePoint 2013 Excel services

    Hello:
    What features are we missing when using Excel 2010 (rather than Excel 2013) with SharePoint 2013 Excel services?
    Regards
    Jeff Gorvits

    Hi Jeff,
    You might want to read the articles below:
    https://support.office.com/en-us/article/Whats-new-in-Power-View-in-Excel-2013-and-in-SharePoint-Server-8e3b4259-421e-41fc-a48e-854388ad14d0?ui=en-US&rs=en-US&ad=US
    https://support.office.com/en-us/article/Version-compatibility-between-Power-Pivot-Data-Models-in-Excel-2010-and-Excel-2013-188f44fd-3cfd-4aa7-b4e6-a9402653cbf3?ui=en-US&rs=en-US&ad=US
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • SharePoint 2013 web service: Error while sending claim based authentication request (The corresponding SID in the domain is not part of the intended account type)

    We are using .asmx services for SharePoint features such as comments, and rating.
    Service
    Feature   used
    http://<<hostname>>/_vti_bin/socialdataservice.asmx
    Commenting, Rating
    http://<<hostname>>/_vti_bin/UserProfileService.asmx
    For out of box workflows
    In SharePoint 2013,
    SharePoint – 80  web application is on claims based mode and user is logging in with windows authentication. With logged-in client context used to call SharePoint's default web service, we are getting below error message from
    web service (Social data and user profile services).
    Server was unable to process request. ---> The corresponding SID in the domain is not part of the intended account type.
    When the service is accessed using console application with Visual Studio credentials (logged in user), we are able to access the service. Below is the code snippet
    using   (SocialDataService
    service = new  
    SocialDataService())
                      service.Credentials =
    CredentialCache.DefaultCredentials;
    SocialCommentDetail detail =   service.AddComment("<<url>>",
      "Test Comment",
    null,  
    null);
    Are SharePoint 2013 web services not supporting request coming with claim based authentication web application?
    Thanks, Pratik Agrawal (MAQ Software)

    While this applies to 2010, I believe the same is true with 2013:
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/925e5f46-317f-46d3-bc55-c67f07eb2372/call-sharepoint-web-services-using-claimbased-authentication?forum=sharepointgeneralprevious
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Backup Sharepoint 2013 Farm with SQL 2012 "Always On" using System Center 2012 R2 Data Protection Manager

    Is backing up and Restoring SharePoint 2013 Farm with SQL 2012  "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
    I cannot find confirmation anywhere.
    Regards,
    John

    Per this thread
    http://social.technet.microsoft.com/Forums/en-US/0c047737-4733-4ad5-a24d-3e6e6ff42f70/dpm-2012-sp1-and-sharepoint-2013-on-a-sql-2012-alwayson-ag?forum=dpmsharepointbackup, no it does not look like this is supported.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Sharepoint 2013 list view quick edit does not work with out remote API permissions

    sharepoint 2013 list view quick edit does not work with out remote API permissions.
    When I give Use Remote Interfaces  -  Use SOAP, Web DAV, the Client Object Model or SharePoint Designer interfaces to access the Web site it works which is not an ideal situation..
    MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

    This is true. If you use Fiddler to watch the requests from the list view quick edit you can see CSOM calls. For example when changing a value in a cell, when you tab out you will see the SetFieldValue and Update method calls on the list item.
    Blog | SharePoint Field Notes Dev Tools |
    SPFastDeploy | SPRemoteAPIExplorer

  • SharePoint 2013 Enterprise and SQL Server 2012 Standard edition vs. Enterprise - feature question

    I can't seem to find any clear answers to the implications of installing SQL Server 2012 standard edition vs. enterprise in regards to SharePoint 2013. 
    I understand that to get many of the features you need Enterprise edition of SQL 2012; but, what I can't figure out is if the backend SharePoint SQL 2012 is standard; but, the PowerPivot/SSRS server is Enterprise will we still get the features?
    If we have 3 tier SharePoint farm, one of those tiers is for the SQL Server database backend.  If that SQL instance is 2012 standard and we add another server to the farm w/ SQL 2012 Enterprise to handle the tabular models, PowerPivot, and SSRS in integrated
    mode will we still get the features?
    Or, can we (should we) install Enterprise 2012 as the SharePoint database backend and let that instance triple down as also the PowerPivot and SSRS instance?
    The Degenerate Dimension

    Hi MMilligan,
    SQL Server 2012 Standard is not supported PowePivot for SharePoint . In addition, SQL Server 2012 Standard is also not support some Reporting Services Features.
    For more information, please refer to Features Supported by the Editions of SQL Server 2012:
    http://msdn.microsoft.com/en-us/library/cc645993.aspx.
    Install SQL Server BI Features with SharePoint 2013 (SQL Server 2012 SP1):
    http://msdn.microsoft.com/en-us/library/jj218795.aspx.
    If you have any problem, please feel free to let me know.
    Thanks.
    If you have any feedback on our support, please click
    here.
    Maggie Luo
    TechNet Community Support

  • Installed SQL Reporting Services 2012 on SharePoint 2013 Server. SQL Reporting Service not available In the list of runnning services or new service applications

    Hi I'm trying to setup SQL reporting services in a SharePoint 2013 farm consisting of:
    4 WFE's
    4 App Servers (NLB Central Admin x 4 servers)
    4 App Severs for SSRS (Light limited SharePoint services running)
    I've installed SSRS 2012 SP1 by following the guide (http://msdn.microsoft.com/en-us/library/gg492276.aspx) on one of the SSRS SharePoint 2013 servers and ensuring Reporting Services - SharePoint and Reporting Services Add-in for SharePoint Products is selected.
    All completed without errors and I have even upgraded to SP2 for troubleshooting but no joy.
    I've then gone into SharePoint Central Admin and I cannot see SQL Reporting Service available In the list of runnning services on the server I have just installed SSRS on and going to manage service applications I cannot see in the new dropdown menu SQL
    Reporting Services.
    I have ran the following commands in the SHarePoint management shell:
    Install-SPRSService and Install-SPRSSeviceProxy
    and
    get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance
    The reply was that the service was already online on the server.
    So in powershell all seems ok but it does not appear in central administration.
    I have also moved Central Administration to the SSRS SharePoint server too.
    Any other suggestions? Here is the same problem but in SP2010 (http://social.technet.microsoft.com/Forums/office/en-US/6a21cc05-1f9b-49ad-a9bb-44aa5b3ce312/action?threadDisplayName=after-installing-sql-reporting-services-service-for-sharepoint-2012-service-is-not-in-the-list-of)
    In my lab environment of a 4 server SP2013 farm it worked immediately when i installed it on the app server (CA host) so I dont think it is my install strategy.
    I guess my next attempt is to install SSRS on an app server with central administration hosted.
    Thanks

    I had the same issue on 2 different environments.
    I had 2 application servers. One had Central Administration. I installed SSRS on the other one and it never appeared in the Service Applications in SharePoint.
    When I also provisioned Central Administration on the other application server and went to the service applications using Central Admin on that server, the SSRS service application was there.
    Since then I always install SSRS on the server which hosts Central Admin. No issues then.

  • Sharepoint 2013 Intigration with SQL 2012 (REPORTING SERVICES)

    Issue : Reporting services is not functioning with sharepoint 2013..
    I want to integrate the sql server 2012 with sharepoint 2013
    Following features are not connected
    Report Server Mode   : Native ( IT SHOULD BE SHAREOINT)
    Report Service Status : started
    If I remove the Reporting Service (Native) Feature then the Reporting services configuration doesn't show the Instance name while configuring the Reporting services.
    Pls revert soon..

    Hi Trevor,
    Yes I tried.. but the application is still not working..
    It Still seems that the reporting services is running in NATIVE MODE  and not in SharePoint Intigration Mode.
    See the PowerShell - Messages below :
    PS C:\Users\Administrator> Install-SPRSService
    PS C:\Users\Administrator> Install-SPRSService
    PS C:\Users\Administrator> Install-SPRSServiceProxy
    PS C:\Users\Administrator> get-spserviceinstance -all |where {$_.TypeName -like
    "SQL Server Reporting*"} | Start-SPServiceInstance
    WARNING: 'SQL Server Reporting Services Service' is already started on server
    'APINNOIGRECREP1'
    PS C:\Users\Administrator>
    The service is already running..
    While accessing the Reporting services configuration - and connect to default instance - it displays the Mode Native not the sharepoint..
    I already installed the Add-on of sharepoint but still same issue..
    If I remove the Native feature from My SQL server setup. then the reporting service doesn't connect and show the default instance.. Pls help on urgent basis.

  • How to properly create and configure SharePoint 2013 Search service with PowerShell?

    Hello Forum,
    I have installed SharePoint 2013 across three tier servers:
    WFE Server  (Of course, SharePoint is installed here. Bsically this is just a Web server)
    APP Server  (Of course, SharePoint is installed here + Central Admin + Service Apps).
    SQL Server  
    I now want to create and configure the Search service, obviously on the APP Server, But of course the search functionality should work correctly on the WFE server to.
    I want to do this via a proper PowerShell script. I found Spence Harbar's script on: (http://www.harbar.net/articles/sp2013mt.aspx), But it has three problems, and they are as follows:
    1) Spence Harbar himself literally stated on his article that this script is for: "deploying on a single server farm", But what if I have three tier servers? Could anyone please help me out in suggesting the required tweaks in the
    script?
    2) By default Search uses the SP_Farm account, So, How can I change the script to use other dedicated account for the search service e.g. SP_SearchAcc ?
    3) How can I modify the script to specify a default Search center?
    4) Apart from all the three aforementioned point - Is the script missing anything? 
    I would greatly appreciate your inputs - Thanks !

    the only differences are where you place the components.  if you are doing a small server farm with a 1-1-1, most likely you just need to change the script so that you set the index and query processing component on the front end, but the others on
    the app server.  just a 2 second update... just keep in mind this will work, but I am making several assumptions without any knowledge of your farm, users, capabilities. 
    generally, there would be more of a breakout on the topology than that, but im guessing for this farm that you wont have dedicated search servers.  also, a lot depends on # users (rps really), # items in index, size of VMs (RAM for query processing,
    Disk for index, etc, etc), and making sure the topology works for your particular environment and needs. 
    if you want more detailed topology help, which aligns as closely as possible to "best practices" (not that those exist in SharePoint, go ahead and provide the total # users, average/peak RPS for search, current index size, content source types,
    VM specs RAM, CPU, #/Size of drives, HA concerns/priority (obviously isn't, since only 1-1-1)
    Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

  • Sharepoint 2013 Reporting services not fetching data via linked server

    We have a functional SharePoint 2013 farm in production with WFE (Server 1 , windows server 2012) and WFE ( Server 2 , windows server 2012) and SharePoint databases including report server databases on  (Server 3, which SQL Server 2012 on windows
    server 2012)
    Kerberos Authentication is enabled and Windows Authentication happens. Claims to Windows Service seems to work correctly too. No double hop issue. The SharePoint Reporting Services seem to be configured correctly and Reports get generated as expected
    in the following cases.
     1. If data is being pulled from Server A (SQL Server 2008 R2 Server on Windows Server 2008), Report gets generated no issues.
     2. If data is being pulled from Server B (SQL Server 2008 R2 Server on Windows Server 2008), Report gets generated no issues.
    The problem:-
    We have a view on Server A, which is fetching data from Server B. This report does not get generated. Gives an NT/Authority logon failure. Server B is created as a linked Server on Server A. The setting to run under users security context is checked.
    If I execute Query Builder from Report Builder 3.0, the query on the view gets the data and data is displayed in the report for next 10-15 min but after that the connections gets lost or if the user logs out and logs back in, the connection is lost
    again.
    Has some one experienced a issue like this? Can a report not work on a view getting data from linked server? Or I have missed  some thing really important.
    Any help is highly appreciated?
    cheers!
    Rachna
    Rachna

    Hi,
    From your description, my understanding is that you got an error when you clicked System settings after configuring Reporting Services service application.
    What size did you use for the memory? Please make sure the server has enough memory to run SharePoint and all services.
    In addition, please open
    http://localhost:xxxxx/SecurityTokenServiceApplication/securitytoken.svc to check if there is something about this issue.
    Here is a similar post about this issue, please take a look at:
    http://whitepages.unlimitedviz.com/2012/07/setting-up-reporting-services-2012-with-sharepoint-2013/
    As this issue is about Reporting Services, I suggest you create a new thread on SSRS forum, more experts will assist you with SSRS.
    SSRS forum:
    https://social.technet.microsoft.com/Forums/office/en-US/home?forum=sqlreportingservices
    Best Regards,
    Wendy
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Upgrade SharePoint 2007 SSRS integrated mode to SharePoint 2013 Reporting Service (SSRS-2014)

    Hi
    We are upgrading a SP-2007 site with SSRS integrated reports to SP-2013 and SSRS-2014. As there are many changes done in SP-2013, I would like to know if any of the existing SP-2007 reporting service database need to upgraded to SP-2013 or just upgrading
    the SP-2007 content database to SP-2013 and creating a new Reporting Service application will be working fine?
    Thanks,
    Pat

    You'll want to do a few things:
    Export the encryption key from the SSRS Configuration application in SharePoint 2007.
    Migrate the content database from SharePoint 2007 SP2+ to SharePoint 2010, to finally SharePoint 2013.
    Install SSRS 2012 SP1+ on SharePoint 2013.
    Migrate the SSRS databases to the SharePoint 2013 SQL Server.
    Create a new SSRS Service Application in SharePoint 2013 using the same named databases on the new SQL Server.
    Import the encryption key to the SSRS SA.
    http://msdn.microsoft.com/en-us/library/jj219068.aspx
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Install SharePoint 2013 database on SQL server 2012 SP1 cluster

    Good Day all,
    We are trying to install SharePoint 2013 database on a SQL server 2012 Enterprise with SP1 cluster (configured for mixed mode) but the connection is not working (times out). We can telent the SQL cluster network name on port 1433 and we made
    a UDL connection file, test the connection via windows authentication and it is working, but if we use the sql authentication it is not working.
    Also we have two SharePoint 2013 servers connected via NLB.
    Any idea about this issue guys?  

    event if 3355 means 3 things:
    The SQL Server might be offline.
    The SharePoint Foundation database access account might not have the necessary permissions to communicate with the SQL Server.
    A firewall that runs on either the local server or on SQL Server might be blocking network communications.
    Big question, how you trying to connect SQL  windows or sql authentication? is it throwing error on Config wizard or somewhere else?
    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Maybe you are looking for