SQL Standard vs Enterprise Edition for SharePoint 2013

Do all SharePoint 2013 BI features come with SQL Server SP1 Standard Edition?
Is there any difference if I install SharePoint 2013 on SQL standard edition rather that enterprise edition?

No, all BI features come with the Business Intelligence or Enterprise version. Take a look at http://msdn.microsoft.com/en-us/library/cc645993.aspx.
Yes, there is a difference in how databases are handled when not dealing with BI features. The two largest examples are the lack of being able to snapshot databases (for content database or site collection backups) or perform an online reorganization of
indexes in Standard.
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.

Similar Messages

SQL Server Web Edition for SharePoint 2013

Dear Expert,
I'm not sure SQL Server Web Edition is ok for SharePoint Server 2013 or not. If I do in On-Premise or Azure.
Please suggestion.

There is no specific document that specifies that Web edition is supported. However, if you look at the requirements list for SharePoint 2013 you will notice that it specifies that it must be either SQL server 2008 r2 with SP1 or SQL 2012.
It also specifies the 64 bit version. But it doesn't specify a specific edition. That and the fact that it will run on SQL Express suggests that it will run on any edition of SQL as long as its 64 bit and a late enough release.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

SQL 2012 AlwaysON High Availability for SharePoint 2013

Our Company have 2 Webfront Servers for Sharepoint 2013 and one Database SQL 2012 Server.
We got one more Server & we don't have Storage so need to configure Always On.
There are Some Confusions:
1- Database Server is in production, so how much down time required to Achieve the AlwaysOn?
2- What are the Changes need to be done on Production Server?
3- What are the Steps to be followed While Configuring new Database Server?
Regards,

Hi Genius1985,
According to your description, you want to configure a SQL Server 2012 AlwaysOn Availability Group for your database, right?
Question 1: Database Server is in production, so how much down time required to achieve the AlwaysOn?
There is no a certain downtime for AlwaysOn, it depends on the configuration of our AlwaysOn Availability Group, normally it can be several seconds or minutes. In order to understand why there is downtime for SQL Server with Microsoft Clustering, please refer
to the following article:
http://www.mssqltips.com/sqlservertip/1882/understanding-why-there-is-still-downtime-for-sql-server-with-microsoft-clustering/
Question 2 and 3: What are the Changes need to be done on Production Server? What are the Steps to be followed While Configuring new Database Server?
Since AlwaysOn Availability Groups require a Windows Server Failover Cluster, we first need to add the Windows Failover Cluster Feature to all the machines running the SQL Server instances that we will configure as replicas.
Once the Windows Server Failover Cluster has been created, we need to proceed with enabling the AlwaysOn Availability Groups feature in SQL Server 2012. This needs to be done on all of the SQL Server instances that we will configure as replicas in our
Availability Group.
For more details about Step-By-Step: Creating a SQL Server 2012 AlwaysOn Availability Group, please refer to the following article:
http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating-a-sql-server-2012-alwayson-availability-group.aspx
If you have any question, please feel free to let me know.
Regards,
Jerry Li

Search Service Application problems after upgrading from Foundation to Enterprise edition of SharePoint 2013

Hi all. I have been searching for days for a solution to a problem I am having with SP2013 Enterprise edition.
We recently upgraded from SP2013 Foundation to SP2013 Enterprise. After the upgrade, the search services are no longer working and we are receiving many application log entries indicating the following:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Technical Support Details:
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
as well as:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
I have tried to remove the search service application and recreate it, and even though the SharePoint Central Administration states that it was created successfully, I am still getting the same errors in the log. If I go to the Search Service Application
Search Administration page, the "System Status" shows the following message:
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '0359af35-0982-4ede-8838-b1d390e915bf' in search application 'Search Service Application' is in a good state and
try again
Additionally, under the "Search Application Topology" section, it states "Unable to retrieve topology component health states. This may be because the admin component is not up and running" which I assume is normal if the admin is not
running.
Does anyone know how I can resolve this problem?
Thanks!

Hi Joaquin,
According to your description, the error occurred when you re-created the Search Service Application.
Based on the error message, I recommend to verify the things below:
   1. Check if the association between the Search Service Application proxy and the web application is configured.
Please go to Central Administration > Application Management > Configured service application associations > Click Default to see if the Search Service application is checked.
   2. Change the app pool for the Search Service Application to SharePoint Web Services Default in the properties of the Search Service Application.
Please go to Central Administration > Application Management > Manage service applications > Highlight the Search Service Application > Click Properties in the ribbon > Change
the two app pool to SharePoint Web Services Default: App Pool For Search Admin Web Service and Application Pool for Search Query and Site Settings Web Service.
    3. Run PS command to check if the search admin timer job is enabled: Get-SPTimerJob
job-application-server-admin-service | fl. If it is not enabled, use PS command to enabled it and then reset Internet Information Services: Enable-SPTimerJob job-application-server-admin-service.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Standard intranet requirement template for SharePoint 2013 online Site

Hi, we are doing requirement gathering of one big markets operator company and planning to build one SharePoint
site using SharePoint 2013 online technology.
Now, we are looking for one standard document to showcase standard features should be in that portal based
upon based on customer need, industry trends and practices for standard intranet build.
Any similar template document will be helpful. Thanks!

Hi Shailendra,
Could you please tell me the detailed customer need ? As different customer need will have different industry trends and practices.
Thanks
Best Regards
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]

SQL 2012 SP1 Reporting Services for SharePoint (2013) - Install-SPRSService Not Available

So, at this point, I've blown away an otherwise functional SP2013 + SQL2012SP1 multi-server farm trying to get this to work, only to end up with the same results. Irrespective of whether I install Reporting Services before or after the SP2013 server is in
a farm, SSRS does not seem to be enabled in the farm. I cannot add a new SSRS service application (the menu item does not exist); I cannot start the SSRS service on server (because it isn't here); I cannot execute the Install-SPRSService cmd in SP (yes, the
SharePoint) Powershell (PS comes back with this error:
Install-SPRSservice : The term 'Install-SPRSservice' is not recognized as the
name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ Install-SPRSservice
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Install-SPRSservice:String) [],
CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Quite simply, something's broken. I've followed a couple of detailed how-to's on technet and elsewhere... Right at the point when I should be able to create the SSRS service application, the wheels come off the cart. I've tried Import-Module'ing the SQLCMDLETS
and SQLPS PS modules...nothing... The strange thing is that after the installation of the SSRS, if I happen to go into the General Application Settings in Central Admin, I see a new item after Content Deployment:
$Resources:ReportServerResources,AdminReportServerGroupTitle;
$Resources:ReportServerResources,ManageIntegrationSettings; |
$Resources:ReportServerResources,AddTrustedAccounts; |
$Resources:ReportServerResources,SetServerDefaults;
When I uninstall, this goes away.
Greatly appreciate any suggestions you can offer because this is driving me crazy, and I have tried everything I can think of to get this going...

Make sure you are running SharePoint 2010 Management Shell not PowerShell.
Also make sure you are running SharePoint 2010 Management Shell with administrator privileges. Right click the icon and click, "Run As Administrator".
You must have installed "Reporting
Services add-in for SharePoint Products" on the server where you are executing "Install-SPService".
You also may be interested to check this tutorial: Install
Reporting Services SharePoint Mode for SharePoint 2013

SQL Server 2000 Enterprise Edition Compatability with Latest Operating Systems

Hi Team,
My client is using SQL Server 2000 Enterprise edition for the database in the Production.
Now,We are planning to load that data from SQL 2000 to SQL 2012 and test the functionality.
Can you please tell me on which operations systems the SQL Server 2000 is compatible to Install ?
like Windows Server 2012/ 2012 R2/ Windows 7/ 8 etc.
Thanks
Srikrishna

Installing SQL Server 2000 on Windows 2008 or later is not supported, but your question is about compatibility rather than support. SQL Server 2000 may work with the database engine but not with some other features and you'll probably need
to click through warnings installation. Proceed at your own risk if you want to go down that path.
I suggest you install on Windows 2003 for your migration testing to avoid obstacles. Not that support ends for Windows Server 2003 in a few months.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

SQL Server Standard Edition with Sharepoint 2013 Enterprise

Hi there,
I need some help figuring out what will be the ideal SQL Server Standard Edition that can run all features for SharePoint 2013 Enterprise Edition. I ordered CAL licenses for a Sharepoint 2013 Enterprise Server (Supports 500 users). Now I need to find out
if it is worth upgrading SQL server to the following:
Upgrade to SQL Server Standard R2 2012 or upgrade to SQL Server Standard 2014? Basically, I am looking for the pros and cons?
-Esteban
Microsoft manager to programmer: You start coding. I'll go find out what they want ...

Hello,
PowerPivot for SharePoint is a feature available only if SQL Server Enterprise Edition and Business Intelligence Edition is used. Reporting Services of SQL Server Standard has also some limitations that will impact SharePoint 2013.
Additionally, SQL Server Standard Edition do not offer AlwaysON, database snapshots and online index rebuild.
To me, the biggest difference between SQL Server 2012 Standard Edition and SQL Server 2014 Standard Edition is that SQL 2014 Standard now supports 128 GB of RAM. SQL Server 2012 Standard is limited to 64 GB.
https://msdn.microsoft.com/en-us/library/cc645993.aspx#CrossBoxScale
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Which version of sql server 2012 or 2014 is best for sharepoint 2013.. Any excellent comparision available please let me know..

Which version of sql server 2012 or 2014 is best for sharepoint 2013.. Any excellent comparision available please let me know..i mean enterprise version BI version or standard version.. i just need a detailed comparison if available please thank you

As of right this very second, SQL Server 2014 is not supported. SharePoint 2013 supports:
One of the following:
The 64-bit edition of Microsoft SQL Server 2012.
The 64-bit edition of SQL Server 2008 R2 Service Pack 1
Hardware and software requirements for SharePoint 2013
Edit: I may be mistaken. It looks like the April 2014 CU adds support for SQL Server 2014. If this is the case generally going with the latest SQL Edition provides you with the latest SQL functionality. I'm not aware of any SharePoint features that would
make use of functionality that is new to SQL Server 2014 but this could change with a future service pack.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Installing Powerpivot for Sharepoint 2013 with SQL Server 2008 R2

Hi,
We are currently setting up a Sharepoint 2013 Enterprise farm with the backend database server being SQL Server 2008 R2 SP2 - my question is can you install Powerpivot for Sharepoint 2013 in this configuration and if so what are the steps?
Thanks in advance!

Here is Microsoft's documentation to Configure Power Pivot for SharePoint 2013
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

SQL server requirement for sharepoint 2013

Hello All,
currently i have installed SharePoint2013 in server farm mode, and i have used SQL Server 2008 R2 for DB. Can i use SQL Server 2012 for SharePoint 2013?
Thanks

SharePoint 2013 is compatible with SQL 2008 R2 and SQL 2012 so yes.
What you can do is "move" the SharePoint DBs from SQL 2008 R2 to SQL 2012 without restore or backup.
Link to msdn: https://technet.microsoft.com/en-us/library/cc512725(v=office.15).aspx
Here you have an example for SharePoint 2010 (is the same for SharePoint 2013): http://www.codeproject.com/Articles/664029/Migrate-SharePoint-s-SQL-Server-to-another-SQL-Ser
Here an different example: http://surya20p.blogspot.com.es/2013/09/migrate-sql-2008r2-sp2-to-sql-2012-sp1.html
Best regards.

Limitations for upgrading SQL server database engin from SQL 2008 R2 enterprise edition to SQL 2014 enterprise edition

Dear All,
we are planning to upgrade SQL Server 2008 R2 Enterprise edition to SQL Server 2014 Enterprise edition.
please suggest the limitations for the up gradation.
Thanks in Advance
Vineet Srivastava
NIIT Technology Ltd.
New Delhi , India

Hello,
Please note that we have 2 Enterprise Editions now:
(1) Enterprise Edition with Server + Client Access License (CAL) and (2) the Enterprise Edition licensed by core. “Enterprise Edition with Server + Client Access License (CAL) based licensing (not available
for new agreements) is limited to a maximum of 20 cores per SQL Server instance. There are no limits under the Core-based Server Licensing model”. Source:
https://msdn.microsoft.com/en-us/library/ms143760(v=sql.120).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Which .exe file I should choose to apply SP2 for SQL Server 2008r2 Enterprise Edition 64Bit

Hi All,
Which .exe file I should choose to apply SP2 for SQL Server 2008r2 Enterprise Edition 64Bit.
And what is the difference between below .exe files.
SQLServer2008R2SP2-KB2630458-x64-ENU.exe
SQLServer2008R2SP2-KB2630458-IA64-ENU.exe
Grateful to your time and support. Regards, Shiva

Good day
Shiva Shakthi,
I have change the type of the thread to a question, as this is a question :-)
please chose the right type next time. If you have a question then use a question thread (this is the default), and that will let you mark the answers that you get.
Have a nice day :-)
[Personal Site] [Blog] [Facebook]

Can we use SQL Server as a primary data storage for SharePoint 2013?

Is it possible to use external SQL Server as a primary data storage for SharePoint 2013?
Having this implemented we can generate reports, query data and it would become very very powerful to use.
Or
Is there a way to keep on using existing content databases and using external SQL Server as a secondary data storage at the same time. So I want it to be like redundant data in SQL Server.
Thanks

Hi，
Not sure if I understand your question correctly, SharePoint has its own content database storing SharePoint list data, we can use SSRS/SSAS integated with SharePoint mode to use sharepoint list as datasource to generate reports.
http://technet.microsoft.com/en-us/library/bb326358(v=sql.105).aspx
http://sqlmag.com/business-intelligence/delivering-bi-through-sql-server-and-sharepoint
http://www.mssqltips.com/sqlservertip/2068/using-a-sharepoint-list-as-a-data-source-in-sql-server-reporting-services-2008-r2/
Thanks
Daniel Yang
TechNet Community Support

Can you replicate databases from SQL Server 2014 Enterprise Edition to SQL Server 2014 Standard edition?

Hello,
Can you replicate databases from SQL Server 2014 Enterprise Edition to SQL Server 2014 Standard edition?
Thanks.

Yes, you can replicate from Enterprise edition to Standard edition. The only caveat is Peer-to-Peer Replication requires all nodes to be Enterprise Edition.
Brandon Williams (blog |
linkedin)

SQL Standard vs Enterprise Edition for SharePoint 2013

Similar Messages

Maybe you are looking for