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

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.

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.

Using BizTalk Enterprise Edition 2009/2013 with SQL Server Standard Edition vs Enterprise Edition

Hi All,
I would like to know what are the Drawbacks of using BizTalk Server Enterprise Edition 2009/2013 with SQL Server Standard Edition vs Enterprise Edition.
We are currently using Enterprise Edition.
1) Are there any adverse performance constraints? Microsoft mentions to use SQL Server Enterprise Edition for "Optimal Performance" but does not expand on the topic.
2) Any features missing?
2) Is there a supported way to downgrade SQL Enterprise to Standard for an exisiting BTS Environment?
Thanks!

1) SQL Standard is limited to 4 CPU's and 64GB of memory while Enterprise is 8 CPU and 2TB or memory.
2) The only BizTalk feature dependency on a SQL Enterprise feature is BAM Real-Time Aggrigations which requires Analysis Services RTA.
3) Yes, but it's not a SQL downgrade really, you would move the BizTalk databases:
http://msdn.microsoft.com/en-us/library/aa559835.aspx

Error in sql 2008 reporting services with sharepoint 2013

i have database sql 2008r2 and sharepoint 2013 enterprise
database is in cluster server and sharepoint have 2 servers one for webfront end and one for services.
im tring to configer ssrs in the web front end server for sharepoint and i install sql 2008 add on for sharepoint 2010 but still have this error
The configuration parameter SharePointIntegrated is set to True but Share
Point Object Model cannot be loaded. The error was:
System.IO.FileNotFoundException: Could not load file or assembly
'Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot
find the file specified. File name: 'Microsoft.SharePoint, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c' at
Microsoft.ReportingServices.SharePoint.Objects.RSSPImpSecurity.set_StaticCatchAccessDeniedException(Boolean
value) at
Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelper..ctor() at
Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelperFactory.get_ServiceHelper()
WRN: Assembly binding logging is turned OFF. To enable assembly bind failure
logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]
(DWORD) to 1. Note: There is some performance penalty associated with assembly
bind failure logging. To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog]. .
(rsSharePointObjectModelNotInstalled)
and befour that i was install sql 2012 add on for sharepoint 2013 but was the same error so i did uninstall for it
this error when i try to open reporting services url
Thanks for any help :) my blog is: http://www.waelk.com

SharePoint 2013 only supports SSRS 2012 SP1 - http://msdn.microsoft.com/en-us/library/gg492257.aspx. You'll need to upgrade your SSRS instance to 2012 SP1.
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 Encryption in SQL Server Standard Edition

Hello,
I need experts advice on Backup encryption options available in SQL Server 2008 R2 Standard Edition. I know TDE is available, but only in Sql Server 2008 R2 Enterprise edition. But we are using Standard Edition.
Thanks

Password protect is not the same thing as encryption - the data is still clear text. This is what Books Online for SQL Server 2008 say about the password option:
"The protection provided by this password is weak. It is intended to prevent an incorrect restore using SQL Server tools by authorized or unauthorized users. It does not prevent the reading of the backup data by another method or the replacement of the password.
This feature will be removed in the next version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. "
And in 2012 this option is indeed removed from the backup command.
Tibor Karaszi, SQL Server MVP |
web | blog

Use parameters in SQL Server reporting services with sharepoint lists

I want to make report from sharepoint 2010 list and forms library in sql server reporting services.
but also want to apply parameters.
I tried but parameters but it is not working.
How I can apply sharepoint lists parameters in sql server reporting services ?
How to run or view report of sharepoint lists or form library in sqlserver reporting services with required parameters?

Hi John,
When we use SharePoint list as datasource in SSRS it has two method to add parameter. Suppose we have a dataset (DataSet1) get data from SharePoint list. Please refer to the methods below.
Method 1: We can add parameter in the Query Designer dialog box to add parameter.
Click “Add Filter” icon in the “Applied filters” dialog box in Query Designer.
Select the corresponding field (Title), fill with specific conditions, and select Parameter option in the end of the row.
Create a dataset (DataSet2) fill with Title field.
Double click the parameter we create above, set the available values from DataSet2 field Title.
(Note: In the situation, we are get the single-value parameter.)
Method 2: It is a general method to add parameter in SSRS report.
Create another dataset (DataSet2) in the report fill with Title field.
Add a parameter (Title) get available values from DataSet2 Title field.
Add filter in the DataSet1.
(Note: This method, we can configure multi-values parameter.)
Reference:
http://technet.microsoft.com/en-us/library/aa337432(v=sql.105).aspx
If you have any questions, please feel free to let me know.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

SQL Server Report integrate with SharePoint slow

Dear Team,
I have SQL Server report servie integrate with SharePoint mode, create several reports and deployed to SharePoint, use SharePoint sql server report viewer web part to view the report.
the report contain about 8 parametes, it takes half a minute to load the report parameters, which is not accepted.
What can I do to improve the performance.
Thanks,

Hi, qq_w
First of all I suggest catching the result
query and running it with the "View execution plan" option so you can understand what is slowing you down. Perhaps you miss some indexes or something.
Secondly, it will be good to run it with tuning advisor.

Office Web Apps Server Name issue with Sharepoint 2013

I have a POC Lab setup for SharePoint/OfficeWebApps with SSL offloading. I am using IIS reverse proxy for my SSL offloader. Most systems can connect to SharePoint and OWA through the Loadbalancer and create documents as desired. The
configuration is as follows:
DNS points:
sharepoint.contoso.com to the reverse proxy address that handles sharepoint.
owa.contoso.com to the reverse proxy address that handles owa.
My OfficeWebApps farm uses an internal and external url of
https://owa.contoso.com and uses ssloffload.
My SPWOPIBinging connects to owa.sharepoint.com (through the reverse proxy) and is configured with the external-https zone.
The name of the OWA server is nyc-owa1.contoso.com.
The issue is as follows:
If I flush my dnscache before connecting to
https://sharepoint.contoso.com, and then use OWA in sharepoint, my client DNS cache will list sharepoint.contoso.com, owa.contoso.com AND nyc-owa1.contoso.com!
Where is is getting the name of the actual owa server?
If I simulate an Internet client that cannot resolve the internal name nyc-owa1.contoso.com, but only the public names of sharepoint.contoso.com and owa.contoso.com, the client cannot successfully edit a new or existing file with OWA, the browser hangs with
Java errors ('SYS' is undefined etc.)
When I add either the real IP address of the server nyc-owa1.contoso.com OR the reverse proxy address for nyc-owa1.contoso.com to a hosts file, the client works normally.
I would like to know how the client is getting the OWA server's name and how to control that behavior.
Thanks for reading this!!
-Scott

I'm glad to here that the problem has been fixed. Thank you for sharing your experience here, it will be helpful to other community members who have similar questions.
Cheers,
Steve Fan
TechNet Community Support

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

Downgrade SQL Server 2008 Enterprise to SQL Server2008 Standard Edition

I would like to know from fourm users, what are the necessary steps I would take care for above mentioned activity and also please let me know best suitable option for Production.
SNS

You can't do in-place downgrade. You need to go with backup -> uninstall ent -> install std -> bring it to same patch -> restore databases approach.
You need to make sure that there is not enterprise only feature used else you can't restore database on standard.
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
Balmukund's answer above is the Microsoft supported route for doing a downgrade of an instance of SQL Server. However, before you do this, you need to query the sys.dm_db_persisted_sku_fearures DMV in each of your user databases to make certain that
you don't have any Enterprise features in use that would block your ability to restore a database onto Standard Edition.
No matter what you are going to have to do an uninstall and reinstall of the SQL Server instance to downgrade the SKU. However, you can save yourself some time and the headache of trying to restore the system databases if you are careful about what
you do. I have done a couple of SKU downgrades in the past and the easiest way to do it, and I am not saying this is the Microsoft supported way but that it works if done correctly, is to:
Take a good backup of all of your databases (system and user).
Run SELECT @@VERSION and note the specific build number of SQL Server that you are currently on.
Shut down your existing instance of SQL Server.
Copy the master, model, and msdb database files (both mdf and ldf), don't move them copy them, from the current location to a new folder that you mark as readonly.
Uninstall SQL Server from the system.
Reboot the server.
Install SQL Server Standard Edition.
Apply the necessary Service Pack and/or Cumulative Updates to bring the instance up to your previous build number.
Shutdown SQL Server.
Copy the master, model, and msdb database files (both mdf and ldf) from the folder you saved them in to the correct location for the new install and remove the readonly flag from the files, and change the file ACL's so that the SQL Service account has Full
Control over the files.
Startup SQL Server and if you did it correctly it will startup and be exactly where you were before you made any changes, with all of your user databaes online and you should be ready to let applications connect and resume operations.
If you screw something up in the above, you still have your backups and you can run setup to rebuild the system databases and then go about following the Microsoft supported path for restoring the system databases and then user databases into the system
to bring it online. Essentially the file copy is no different that what would occur through attach/detach you are just doing it with system databases which is not supported, but it does work. The key is to have your backups from before you do anything
so you have the supported route available if you encounter an issue. The only issue I have ever had doing this set of steps is that I didn't set the file ACL's correctly and the database engine threw Access Denied errors and failed to start until I fixed
the ACL's correctly. This can save you many hours of frustration and downtime trying to restore everything since the database files are already there and it is just some small copy operations to put them where you need them to be.
Balmukund, feel free to beat me over the head for suggesting a non-supported path. :-)
Jonathan Kehayias | Senior Consultant,
SQLSkills.com
SQL Server MVP | Microsoft Certified Master: SQL Server 2008
Feel free to contact me through
My Blog or
Twitter. Become a
SQLskills Insider!
Please click the Mark as Answer button if a post solves your problem!

Office Web Apps 2013 with SharePoint 2013 Server

Hi All,
I have installed a separate server for Office Web Apps 2013 on Windows Server 2012 VM. I have followed TechNet's article on
Deploying Office Web Apps Server & exactly followed steps.
On SharePoint Server 2013 (Windows Server 2012), I followed TechNet’s article on
Configure Office Web Apps for SharePoint. The Office Web Apps on SharePoint 2013 environment works for
Excel document that shows “View in Browser” but
no Preview.
However, PowerPoint and Word documents doesn’t show “View in Browser”. I thought Internet Explorer 10 has some issue with Office Web Apps and checked on Chrome and results were same.
On SharePoint Server 2013 environment, I have configured 3 services applications, MMS, UPS and Excel Service.
1.) Do I need any other service applications to be enabled for OWA 2013?
I read number of blogs,
Installing Office Web Apps Server for SharePoint 2013 (Steve Mann),
Install Office Web Apps 2013 with SharePoint 2013 (Max Melcher) and Spence Harbar
(Enabling Office Web Apps Preview editing with SharePoint 2013). and all these blogs give more or less same steps that I have followed.
Strange thing is that Excel documents on my SharePoint 2013 sites are working but neither word or PowerPoint documents are not showing option for “View in Browser”.
I am using HTTP and not HTTPS.
2. Can someone please advice how could I solve the Office Web Apps 2010 on Word and PPT?
3. How to can enable preview for Excel, Word and PPT documents.
Thanks you.
Regards,
Aroh
Aroh Shukla

Hi Inderjeet and Olafur,
Thanks for your reply.
@Inderjeet: That site collection feature on SP2010 works on our production environment but on SP2013 site collection there is no OWA feature. Microsoft recommends to have a separate OWA2013 server and what I create
a separate VM for OWA2013 server.
@Olafur: Your suggestion looks spot on. The OWA server does show the discovery:
Our SP2013 development server has limited RAM (4GB) and it think is causing the issue.
Let me check if increasing RAM solves the issue.
Thanks again for your suggestions. (Interjeet and Olafur).
--Aroh
Aroh Shukla

Will BOBJ Enterprise 6.5 SP3 run on Window 2003 server standard edition?

Trying to trace some documentation on system requiremetns for Business Object 6.5 but cannot find any...maybe i'm looking in the wrong place. My query is does anyone know if Business Objects Enterprise 6.5 SP3 will run on Windows 2003 Server Standard Edition with Apache 2.0.50 and Tomcat 5 ?
Thanks
Roy

The answer is YES. Business Objects Enterprise 6.5 SP3 will run on Windows 2003 Server Standard Edition with Apache 2.0.50 and Tomcat 5

SQL Server 2012 Edition required for my case??

Hi,
I am setting up a SharePoint 2013 BI environment with minimal servers. Below is the configuration:
1) WFE1 - Front End Server Role
2) APP1 - Application Server Role with SSRS 2012, SSAS in SharePoint mode.
SQL Server 2012 BI edition is used here for SSRS and SSAS in SharePoint mode
3) DB Server - SharePoint content databases only
- Can this SQL Server be standard edition ? or does this server also need to have minimum BI features which means it should be BI or Enterprise edition?
Thanks
Sandeep
Sandeep Nakarmi www.snakarmi.me

Hi Sandeep,
Thanks for posting your query, Below are the URLs that describe the situation to USE the SQL SERVER Standard or Enterprise Edition for BI features. Kindly go through these URLs once to get the difference.
http://searchsqlserver.techtarget.com/feature/When-to-consider-SQL-Server-Enterprise-Edition
http://searchsqlserver.techtarget.com/feature/SQL-Server-Standard-Edition-Why-its-worth-the-cost
Of course, you will get more features for BI in as sequence SQL Server Edition mentioned below
Express < Standard < Enterprise
Moreover, browse the below mentioned URL to enable BI features in SharePoint
http://blogs.technet.com/b/ldusolier/archive/2014/05/19/use-of-bi-capabilities-in-sharepoint-2013-with-sql-server-2012.aspx
I hope this is helpful to you, mark it as Helpful.
If this works, Please mark it as Answered.
Regards,
Dharmendra Singh (MCPD-EA | MCTS)
Blog : http://sharepoint-community.net/profile/DharmendraSingh

RBS Licensing on a SQL Server Standard 2012 Failover Cluster

I am planning to implement a Sharepoint 2013 installation which is primarily to be used for Document Storage. We are considering using Sharepoint RBS with Filestream with SQL 2012 Standard and as far as I can see on our non-production environments this works
without any issue - i.e. we enable filestream and RBS with Sharepoint and SQL and everything works as expected on our non production systems. In non production we have single SQL Server nodes.
However, in production we have planned to have a 2 node SQL 2012 Standard failover cluster.
On this page, it indicates
"To run RBS on a remote server, you must be running SQL Server 2008 R2 Enterprise on the server that is running SQL Server where the
metadata is stored in the database."
My question is : Am I entitled to use RBS with Filestream on a SQL 2012 Standard Failover Cluster, or is SQL Enterprise required.
If enterprise is required, we will have to remove the RBS. I have reviewed the links below, but cannot see a definitive answer from a licensing perspective
http://social.technet.microsoft.com/Forums/en-US/76e86936-b7ee-4571-aa02-f45b80867515/which-edition-for-sql-server-2008-r2-with-sharepoint-2010-no-foundation?forum=sharepointadminprevious
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2b04979f-c619-48a4-b0e4-3add00345fb0/sql-server-2008-edition-comparisons-in-terms-of-high-availability-rbs?forum=sqldisasterrecovery

Hi antrimcoaster,
Indeed, in Microsoft official document, all SQL editions (Express, Standard, Enterprise…) of SQL Server 2008 and SQL Server 2008R2 support RBS (Remote Blob Store), however, as your post, if you run RBS on a remote server, we recommend you use Enterprise
version especially you want to deploy Remote BLOB Storage with SQL Server 2012 in Production environment. Usually, Enterprise edition is more for mirroring, supporting more RAM/CPU, and custom RBS providers and multiple nodes cluster.
If you had setup and configured RBS successfully with SQL Server 2012 standard, and now you need to want to upgrade to SQL Server 2012 Enterprise, I recommend you reconfigure your blob store, you can review the following similar article.
https://community.dynamics.com/ax/b/axdilip/archive/2012/10/22/configuring-and-implementing-sharepoint-2010-rbs-remote-blob-storage-with-sql-server-2012-part-1.aspx
In addition, for more detailed information regarding to the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please
use the Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.
Thanks,
Sofiya Li
If you have any feedback on our support, please click
here.
Sofiya Li
TechNet Community Support

SQL Server Standard Edition with Sharepoint 2013 Enterprise

Similar Messages

Maybe you are looking for