Configure SQL Server 2. Share. Point 2. 01. If youre using SQL Server 2. Share. Point 2. 01. SQL Server 2. 01. Share. Point 2. 01. If you followed the instructions I provide in Set Up SQL Server 2. Share. Point 2. 01. Database Server, youre just a few steps away from having a SQL Server instance that will serve admirably as the database back end to your Share. Point 2. 01. 3 farm. Related Set Up SQL Server 2. Share. Point 2. 01. Database Server Part 1Related Fine Tune Your SQL Server 2. Configuration for Share. Point 2. 01. 3 Part 3In this article, I discuss the two configuration steps that you must perform to enable SQL Server as a Share. Point database server. In a companion article, Fine Tune Your SQL Server 2. Configuration for Share. Point 2. 01. 3, I explain some optional configuration tweaks that I like to make to my SQL Server instances for optimal performance. Now lets dig into the details. Set MAXDOP to 1. In Set Up SQL Server 2. Share. Point 2. 01. Database Server, we installed a SQL Server instance, but there are a few tweaks we need to make before that instance can work with your Share. Point 2. 01. 3 setup. To perform these tweaks, your first step is to log into SQL Server as an account that has elevated permissions to the SQL Server instance. This post is applicable only to SQL Server 2012, SQL Server 2012 SP1 with SharePoint 2013 SP1. Before you implement RBS, I highly recommend that you. Microsoft has released an update for Microsoft SharePoint Enterprise Server 2013. This update provides the latest fixes to Microsoft SharePoint Enterprise. Well that is another confusing issue. I dont believe there is a metro IE. When I click on the IT tile, it goes to the desktop IE. I have Windows 8 and the. Lists the steps to install BizTalk Server. Account names with BAM Management Web Service BizTalk Server does not support builtin accounts or accounts without. Summary Configuring Exchange Server 2013 and SharePoint Server 2013 for task synchronization by using the SharePoint Server 2013 Task Synchronization feature. SharePoint Server 2013 known issues Support Office. SharePoint Server 2013 known issues Welcome to Microsoft SharePoint Server 2013. Please refer to the. In the accompanying video, I logged in and made the tweaks via the sqlinstall account that I used to install SQL Server. After SQL Server is installed, open SQL Server Management Studio SSMS. KB/sharepoint/440608/image013.jpg' alt='How To Install Sharepoint 2013 On Windows Server 2012' title='How To Install Sharepoint 2013 On Windows Server 2012' />With the exception of the last tweak I suggest, all the changes are made to the SQL Server instance. To access the instances settings, right click the instance name and click Properties from the flyout menu. The first change I make after SQL Server 2. MAXDOP to 1a setting that is a requirement for creating the Share. Point 2. 01. 3 farm. This required setting is new in Share. Point 2. 01. 3 in Share. A9GP.png' alt='How To Install Sharepoint 2013 On Windows Server 2012 R2' title='How To Install Sharepoint 2013 On Windows Server 2012 R2' />Point 2. MAXDOP to 1 was only recommended. By default MAXDOP is set to 0, which tells SQL Server, Parallelize as much as your bad self wants to. To change the setting to 1, in the properties for the SQL Server instance, go to the Advanced tab. Youll find the MAXDOP option under the Parallelism group, as shown in Figure 1. Set it to 1 and click OK. Figure 1 Setting Max Degree of Parallelism to 1 in SQL Server 2. What exactly is MAXDOP, anyway, and why is it so important to Share. Updated Version Let us see How to Install Exchange 2013 Sp1 on Windows Server 2012 R2 You can Download the Exchange Setup Sp1 from the Below Link Microsoft Exchange. In this post, Ill guide you trough the process of installing Windows Server 2012 R2, SQL Server 2014 CTP1, and on top of that the brand new TFS 2013 that was. How To Install Sharepoint 2013 On Windows Server 2012' title='How To Install Sharepoint 2013 On Windows Server 2012' />Point MAXDOP is a setting that defines how many CPUs SQL Server uses when its executing a query. Thats great, if the queries were written to take advantage of that setting. If they werent, splitting the execution among multiple processors can have unpredictable results. Unpredictable is acceptable for birthday presents, or the ending to O. Henry stories, but it isnt so good for Share. Point. Share. Point is unpredictable enough on its own without SQL Server pitching in. Because Share. Points stored procedures were not all written to handle parallelism, MAXDOP has to be 1. Set Permissions for Share. Point. The next change I will make in my SQL Server configuration is to give my Share. Point installation account the permissions it needs to create a Share. Point farm and to give permissions to the other Share. Point service accounts. As described in my blog post Service Account Suggestions for Share. Point 2. 01. 3, this account is spinstall. Share. Points demands are pretty reasonableit doesnt need to be sysadmin or anything crazy like that. Spinstall just needs the dbcreator and securityadmin server roles. This makes good sense as spinstall needs to create the farm databases and give the other service accounts permissions. To give the spinstall account the permissions it needs, in SSMS navigate to Security, Logins in Object Explorer. Right click and select New Login. Under General, type the username and make sure you include the domain. Then on the Server Roles page, shown in Figure 2, select the dbcreator and securityadmin check boxes and verify that the public check box is still selected. Then click OK. Figure 2 Assigning Permissions to the spinstall Account. Let me offer a few words of advice about setting the spinstall permissions. Share. Point assumes that those three roles, dbcreator, public, and securityadmin, have the default set of permissions in SQL Server. Dont alter those permissions. Ive seen DBAs in very secure environments try to lock down these three roles. Doing so will most certainly break Share. Point in crazy and unusual ways. That might not happen right away, and it might not happen to you when youre using the interface. It could be a monthly timer job that fails, for instance. Also, dont change any SQL Server permissions that Share. Point sets. Share. Point is very fussy, and if it sets permissions, it really needs them. Because of Share. Points rigidity on its SQL Server permissions, I recommend that you put Share. Point in its own SQL Server instance. Share. Point will thank you, and so will your DBAs. Script Your SQL Server Config Settings. In the spirit of making SQL Server configurations more efficient, I script all the settings Ive described in this article and Fine Tune Your SQL Server 2. Configuration for Share. Point 2. 01. 3. Scripting these changes makes them easier to document and tougher to screw up. It also appeals to my lazy tendencies. Because I make these same changes every time I configure a SQL Server instance, I have a file that contains them, which looks like what you see in Figure 3. Figure 3 Script to Configure a SQL Server Instance. If you click Execute, that script will make all the changes to configuration settings that I covered in this article and Fine Tune Your SQL Server 2. Configuration for Share. Point 2. 01. 3, except the backup compression setting. I forgot to add it. Dont worry, I wont make you type all that yourself. You can download that script, SQLTweaks. If you do decide to script your SQL Server configuration changes, make sure you test them thoroughly. Fancy scripts are a double edged sword. Although they are a great way to quickly and easily make a lot of good changes, theyre also just as apt to quickly and easily destroy stuff. You might be thinking that I must have some mad T SQL scripting skills to figure out how to script each of those settings. If only that were the case In reality, SSMS makes it very easy to turn any series of clumsy mouse clicks into a beautiful T SQL script. In the top left corner of all the dialog boxes is a Script button. Now You Re Cooking Keygen. That magical button takes all the changes youve made to the dialog box and turns them into a T SQL script. As you can see in Figure 4, after I added the correct server roles, but before I clicked OK, I clicked the Script button and scripted my changes to a new query window. I did that three or four times, then copied and pasted each script into one window. I saved those scripts out as SQLtweaks. Internet hero Figure 4 Scripting Configuration Changes to a New Query Window. Share. Point farms support their databases being in multiple SQL Server instances. If you decide to spread your databases across multiple instances, remember to make these same changes to your subsequent instances. If you have your own SQLtweaks. Poking a Hole in the Firewall. Before your Share. Point server will be able to actually contact your SQL Server instance and take advantage of it, well need to make sure that the firewall thats running on your SQL Server instance will allow Share.