SQL Server Security in SharePoint 2013

Using SharePoint for a very long time, it is felt that SQL needs only the most initial configuration, that is no longer required for management and maintenance. And actually. SQL management and security are closely related to the stability of the SharePoint environment, so it is important to take absolute care of the management and maintenance of SQL Server in SharePoint.

This article mainly introduces the following three points:

First, about the permissions of SQL account;

II. Disk Management for SQL Server

III. changes to the SQL Server service port

I. Permissions on the SQL account

The first thing to say is about the account. Whether it is the Sharepointserver field configuration account, or a variety of services account. are required for SQL permissions. There was no more research to be done for the sake of convenience. are directly assigned to all permissions. In fact, SharePoint requires only dbcreator and securityadmin permissions for SQL Server permissions.

II. Disk Management for SQL Server

Second, it's about managing SQL, and when you see this planning in the MSDN documentation, you do feel that you know too little about SQL Server before. Ideally, you should also place the tempdb database, the content database, the usage database, the search database, and the SQL Server transaction log on a separate physical hard disk.

When setting the data priority on a faster disk, use the following rating:
· Tempdb data files and transaction logs
· Database transaction log files
· Search database (except search administration database)
· Database data files

Of course. In addition to the initial setup, regular management and monitoring of database service conditions is also a major feature of SharePoint environment maintenance.

III. changes to the SQL Server service port

At last. What you want to say about Sqlport is that, as we all know, SQL Server defaults to 1433port, so the SharePoint database will be exposed, and many other times we will manually change the port to avoid unsafe features.

There are two main changes, one is the SQL Configuration tool changes:

Open the SQL Server configuration Manager, find the config of aliases, change the default 1433port, as far as I know, just change the second one can, of course, to avoid the problem. It doesn't hurt to change everything.

For example, with:

The second is by altering the registry, as the assumption changes SQL Server communication port. The server and client must be changed at the same time, and the SharePoint front section typically does not install SQL, but you can also install only administrative tools, or change the way you register tables:

Summary

These are some of the key points in SharePoint recently learned about SQL Server security management. Take it out and share it with you, not just the 2013 version number. The previous version number still applies. Of course there may be deficiencies. Need to continue to improve, want to know a lot of other people to give advice. Also hope to bring to the people who need to help.

References link

http://technet.microsoft.com/zh-cn/library/ff607733 (v=office.15). aspx

Http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx

SQL Server Security in SharePoint 2013