What is the time zone set in SharePoint Central Administration?
Go to the following link and see if the time zone matches what you expect:
Also check the regional settings for your Site Collection to see if the correct timezone is set.
There are two ways to look at this concern.
First is to literally take what Microsoft says in face value, because they are most of the time correct about the operational best practices for their own products.
Said so, if you follow the guideline mentioned here
There are several limitations that affect the SharePoint Server 2013 running under SQL Server 2012 express:
You have only one cpu (with 4 cores) available for the sql server
You can only assign 1 GB Ram for the sql server express instance
You have only 10GB per database
It will be harder to scale out your farm later on
The User Profile Sync won't work
There always will be a maximum upload size for each web application, maximum timeout time in IIS for for each IIS site and a lot of other soft limits (thresholds, can be changed), but hard limits (boundaries) can never be changed.
Boundaries are absolute limits that cannot be ...
SharePoint Server 2013 SP1 supports Windows Server 2012 R2. I see no reason why you shouldn't run your SharePoint Server on a 2012 R2 Server. Just make sure you install SP1 correct before adding logic, solutions and content to your farm.
Currently, Microsoft SharePoint Server 2013 is not supported for installation on computers running the Windows Server ...
I have installed tons of SQL-Server Updates on lots of SharePoint farms. SharePoint never got broken.
But if you heavily rely on that environment, you should have a testing-environment that matches prod environment as close as possible. You can install updates there and check if everything works as expected. Checklists are very helpful to standardize this ...
The problem most likely involves a permissions issue and is trivial to resolve.
The account running the MSSQLSERVER service is the one that actually processes the backup. The destination folder for the backup must be configured to specifically allow this account access. Setting access to Everyone is insufficient. The MSSQLSERVER service account must ...
Before the release of Microsoft SharePoint Server 2013 Service Pack 1 (SP1), Microsoft did not support the installation of SharePoint Server 2013 in a Windows Server 2012 R2-based environment. However, with the release of SharePoint Server 2013 SP1, this configuration is supported in Windows Server 2012 R2.
If we are talking SharePoint 2013 and SQL Server 2012 you have the possibility of creating an AlwaysOn cluster for high availability.
I recommend starting with this blog post that will give you a step-by-step guide on how to set it up. Then proceed to read all available articles on TechNet on the subject. This include planning (especially focus on High ...
From a database perspective I think the improved High Availabilty features are the main point.
From a SharePoint point of view the better integration of PowerPivot and Reporting Services are the main things.
And then you have the longer support time as an extra bonus.
But you can go through MSDNs What's New in SQL Server 2012 to look for things which are ...
By default, the SharePoint_Config database is set to Full recovery model. But, Microsoft recommendation is to set the recovery model for your SharePoint_Config database to simple in production (reference: http://technet.microsoft.com/en-us/library/cc678868.aspx). You can change the recovery model for SharePoint_Config after you create the SharePoint_Config ...
This is a cryptographic error. You will need to set permissions on a the crypto keys folder:
The folder is located at:
Alternatively, go into computer ...
You have excellent environment for BI platform with SQL 2012 and SharePoint 2013 enterprise edition.
So my strong recommendation would be to please extend the BI site template to all the other 10 products and make sure you activate the SharePoint enterprise features so that you will be able to utilize the core SharePoint collaboration features along with ...
On technet you can find a article about how to Move content databases in SharePoint 2013
This article describes how to move content databases between servers that are running SQL Server, between instances of SQL Server, or from one SharePoint 2013 web application to another.
The article describes two ways to do this
Moving content databases by using ...
So by Native-mode vs. Integrated Mode you are actually refering to Reporting Services.
I assume you also know that one major implication/difference between the 2 modes is the fact that by example, the reports definition files and Data Sources are stored in the SharePoint Content database. Also, there is no concept of “Report Manager” in SharePoint ...
In my opinion you can use single BI Center site template to manage content for all 10 products site.
In one single BI Center site you can show multiple content of multiple products using score-cards, dashboards, excel BI reports, SQL reporting services reports, PerformancePoint reports, Chart web-parts, etc.
You need to do a little home work and understand ...
It is really doesn't matter which SP you installed First, Rather you have to take the appropriate measure before install the any SP.
For Installing SQL Server SP2, you should shut down the all SharePoint Services so that No connection made to SQL from SharePoint while you updating the SQL Server. We shut down the SharePoint Completely while we applied the ...
If you want to use Active Directory for your accounts, then yes, you need to configure your machines on a virtual LAN and create an Active Directory domain. This is not a simple process and isn't really on topic for this site. You should be able to find tutorials on this process pretty easily using Google.
Does every machine has to have the same ...
This error is occurring because your SQL server is installed on a separate server. In order to make it work you need to give path like
For that you should share the folder first.
Now make sure the SQL server service account has write permission on the backup folder.
As it turned out, I needed to configure an External Content Type Profile Page Host within the Business Data Connectivity Service.
When the ECT Profile Page Host was configured, I could connect to the database and see the tables from the database within SharePoint Designer.
AlwaysOn is a great new feature to SQL Server 2012 that allows consuming clients to have a mirroring and failover database solution all transparently for a single named instance. SharePoint is one such consumer of SQL and depends on having a solid connectivity to run. If SQL goes down, so does SharePoint so it’s well within our interests to configure a ...
I'm pretty sure this wont work. While reporting services is claims aware, you still need Claims to Windows Token Service (C2TWS) to access the data source - even if it's all local. You can't use local accounts with C2TWS because it will do a query to resolve the UPN to match to a claim.
That is happening because you are running a services apppool as Network Service or Local System. That account with the $ at the end is your server's identity.
You can either authorize that account to access the data or run you service applications as a user that is authorized to access the database.
if your Central Admin site root was: http://ca/ then ...
The SQL Server MAXDOP (MAX Degree of parallelism ) should be changed to 1 for SharePoint.
If any other applications are using SharePoint, this will limit the degree of parallelism for those applications, and therefore may impact the performance of the applications.
If you do not change the degree of parallelism, some actions in SharePoint may not be ...
The SharePoint 2013 with SP1 is supported with SQL Server 2012 SP3, so there is not impact on the farm, but this operation will require an outage.
So, it's recommended to
Apply this operation first on a test farm before applying it directly to production.
Apply this operation out working hour.
Take a backup of all SQL Database.
As a short answer: Yes, It's supported,
In order to use Microsoft SQL Server 2012 SP2, you must use
SharePoint 2010 SP1 or later of SharePoint Server 2010!
In order to maintain SharePoint and SQL Server compatibility Microsoft
use the “SharePoint N-1 on SQL Server N+1” equation to determine
version support. Using SharePoint Server 2010 ...
I guess not. You can use SQL Server 2014 but I guess it also will be out of support soon.
SQL Server 2012 with SP4 has extended end of life cycle which will end by 2022. product lifecycle
You have to check with Microsoft account manager for clear dates. You dont need to upgrade to sql 2016 (as it is not supported), you can upgrade to Sql 2014 which is fully supported.
SharePoint Designer does not use the Secure Store connection. Try creating the ECT first by connecting with user's identity. Once the ECT is created, modify the properties to use the Secure Store application ID.