Showing posts with label SQL. Show all posts
Showing posts with label SQL. Show all posts

Thursday, August 6, 2015

Support for SQL 2014 with SharePoint 2013



Support for SQL 2014 with SharePoint 2013

This is a common question arises in every administrators mind. is the SQL 2014 supported by SharePoint 2013?on what extent? Please find the answer as below.

Yes, SharePoint Server 2013 will support SQL Server 2014 with the April Cumulative Update. Find the reference links from MS.
 

 http://www.microsoft.com/en-us/server-cloud/products/sql-server/

http://msdn.microsoft.com/en-us/library/bb500435(v=sql.120).aspx

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Thursday, May 28, 2015

SQL 2016



SQL 2016

 To get to know more on SQL 2016 like below

What are the new features added in 2016?

what is difference between 2014 and 2016?
is any improvements in Services in 2016?
requirements to install 2016?

Please go through the Below Articles that gives much information on all


 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Tuesday, May 5, 2015

SQL account used for SharePoint



SQL account used for SharePoint

When we plan to build the SharePoint, The first and most important part is the account used for the SQL admin. Please find the details below that provide you more information on the account.

1. SQL Admin Account
SQL Admin account would be use to install SQL Server for your SharePoint and would be created in AD. This account should be a domain user and must be a local administrator on database server. These rights are enough to successfully install SQL Server. Do not use any other domain admin account or never make this as a domain admin account. I have seen people using domain admin account to install SQL and SharePoint which is a mistake and a threat to security. You can name this account as "sql_install" or "sql_admin".

2.
SQL Service Account
This is the account that runs the SQL Server instance. This should be a domain user but do not make this as a local administrator for security reasons. You can name this as "sql_user" or "sql_services". While installing SQL Server with SQL Admin account, necessary permission would be granted to this account for running the SQL Server instance. At Server Configurations step during SQL Server installation, mention your SQL Service account as the account for SQL Server Database Engine and SQL Server Browser and automatically necessary rights would be granted to this account to run the SQL Server instance.

3.
SharePoint Setup Account
Create an account "sp_install" (a recommendation, you can name it anything) in your AD and put this account in local administrator group on all SharePoint Servers. Make sure you do not put this account in domain administrator account. You should never use a domain admin account to install SharePoint and its services.
 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Thursday, March 26, 2015

Unknown SQL exceptions - Event 5586



Unknown SQL exceptions - Event 5586

Alert Name:   Unknown SQL exceptions

Event ID:   5586

Summary:   Microsoft SharePoint Foundation uses Microsoft SQL Server 2008 databases to store configuration settings and most of the content for the Web site. For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server 2008.
Microsoft SharePoint Foundation uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name or password (domain name and password), or a predefined system account, such as Local System or Network Service. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases.

Symptoms:   The following symptom might appear:

·         This event appears in the event log: Event ID: 5586 Description: Database full error on SQL Server instance <instance name> in database <database name>. Additional error information from SQL Server is included below. <SQL error message>.

Cause: The issue is because of many reasons, below are some of the reasons
1.    Insufficient SQL Server database permissions
2.    SQL Server database is full
3.    Incorrect MDAC version
4.    SQL Server database not found
5.    Incorrect version of SQL Server
6.    SQL Server collation is not supported
7.    Database is read-only

Solution: The issue could be of many reasons so it has many different solutions that should implement to resolve the issue. One of the solution would be your saver.
Please check the link below from MS to get the solutions.

 https://technet.microsoft.com/en-us/library/ee513056%28v=office.14%29.aspx

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Monday, December 22, 2014

SQL Server Setup or Installation Failure Errors



SQL Server Setup or Installation Failure  Errors 

Issue: SQL Server 2008 R2 setup failed with “Error 1406. Could not write value to key \SOFTWARE. System error. Verify that you have sufficient access to that key, or contact your support personnel”

Run setup as Administrator
Make sure Administrator has full control on the registry key reported in the error.
This issue can happen, if there are any kind of virus/adware/malware/Addons on the system. Scan the system and fix any such issues.
There is a connect bug raised for the same, please check of there are any latest updates.

https://connect.microsoft.com/SQLServer/feedback/details/998266/could-not-write-value-to-key-software-verify-that-you-have-sufficient-access-to-that-key-or-contact-your-support-personnel

Issue: Error 997. Overlapped I/O operation is in progress during SQL Server installation

– Check the account with which you logged on to the server, make sure it is not a account with temporary profile.
– Run the Setup locally on the server and make sure you run the setup, by right-clicking on the Setup file and choose Run-As-Administrator.
– Disable any Anti-virus and reboot the server.
– Check for any problems with the disk drive where you are installing SQL Server files.


Issue: Invalid license data. Reinstall is required Error while trying to connect to SQL Server Management Studio (SSMS)

– Try to repair the SQL Server shared components(If you cannot launch the setup from control panel, use the Setup.exe from setup media.
– After repair, if it SSMS still fail with the same error, then uninstall Visual Studio 2010 or 2012 and then attempt the repair of the shared components again.


 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

ShareThis

X