Starting/Running SQL SERVER 2012 (SQL Permissions) for SharePoint 2013

You need to give the SharePoint Account that you plan to install and configure SharePoint with some elevated rights in SQL. Typically we recommend you use a dedicated account [Domain]\[SharePoint Admin] and this account will need the following roles on the SQL Server.

• DB_Creator
• Security_Admin
• Public

From your newly installed SQL Server click Start > All Programs > Microsoft SQL Server 2012 > SQL Server Management 2012.

After waiting this loading user settings screen will appear:

Wait for some time then the following screen appears:

Login as [Domain]\[SharePoint Admin] by selecting “Windows Authentication”:

From Object Explorer expand-out Security.

Under Security expand out Logins.

In case you don’t have the User

• Right click on Logins.
• From the menu choose New Login.
• For Login name: enter [Domain]\[SharePoint Admin]  or whatever account you will be logged into SharePoint as when you do the install.

After right click, select Properties. The following screen will come:

On the left, under select a page click Server Roles.

Check the box for dbcreator and securityadmin. Also, leave public selected.

Click OK. Now your [Domain]\[SharePoint Admin] is ready to install sharepoint on the server.

Max Degree of Parallelism for SQL SERVER 2012 (before installing Sharepoint 2013)

Now that you have SQL Server all installed there is one more configuration change you need to do in order to make SharePoint happy. You need to change the max degree of parallelism. Don’t ask me what that is. Something about number of processors and how SQL uses them. Unfortunately SQL Server defaults to 0 and SharePoint 2013 necessitates, demands, forces, requires, and otherwise really wants you to set it to 1. So make the change. If you are running SharePoint 2010 this change is not required but is recommended.

Now if you look at the link I gave you saw a bunch of fancy SQL to change it. Barf! Let’s change it the easy way, with a mouse.

From your newly installed SQL Server click Start > All Programs > Microsoft SQL Server 2012 > SQL Server Management 2012.

On the Connect to Server screen click Connect. If for some reason the Server name: field is blank you would just type in the name of the server.

At the top of the Object Explorer window you see your server. Right click on it.

From the menu that appears click Properties.

In the Select a page section click Advanced.

Scroll to the bottom and change Max Degree of Parallelism from 0 to 1.

Click OK.

That does it. No need to reboot or anything else to make the change take effect.

Resolving VS 2010 solution deployment issues for SharePoint 2010 projects

In my new SharePoint 2010 book, I touch base on variety of deployment approaches; in this article I wanted to focus on Visual Studio 2010 feature allowing to deploy SharePoint 2010 solutions right to the portal. However, you haven’t configured your development environment properly – you will run into issues. Here I’m talking about the following error:

Error occurred in deployment step ‘Recycle IIS Application Pool’: The local SharePoint server is not available. Check that the server is running and connected to the SharePoint .

Or this:

Error occurred in deployment step ‘Recycle IIS Application Pool’: Cannot connect to the SharePoint site: http://localhost/. Make sure that this is a valid URL the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since you created the project, update the Site URL property of the project

Visual studio uses the following process to deploy your solution: vssphost4.exe
Open your task manager and find the process in the list; take a note of the User Nameunder which this process is running, let’s say it’s myadmin_account

Now, open your SQL Management Studio and ensure this Username is added as a DBOWNER to the following databases:

SharePoint_Config
SharePoint_AdminContent_[guid]
SharePoint Site Content DB

Close and Open your Visual Studio again, this will ensure the service is recycled; this should fix above deployment error. If you’re still having same issue, End the process in taskmanager and then VS 2010.

Good luck!

Ref : Sharemuch

Creating Permission Levels in MOSS

Some days ago I was asked about how to allow users to add forms to a forms library without having to grant users the Contributor role because with this permission level the users have also rights to change other’s forms.   The answer is that the users only need Add and Read permission to add new forms to a Forms Library and the ability to read them.  What I forgot when I was giving my answer was how to create a permission level and add these rights to the new security schema.  The “quick recipe” about how to create a permission level will be:

1. Go to Site Action Menu.
2. On that menu, go to Site Settings.
3. Choose People and Groups
4. On the quick launch bar, there is a link to Site Permissions.
5. On the Settings menu, click over Permission Levels.
6. On the Permission Level page, you can click over new and create a new permission level.
7. Add the permission that you want (in this case, Add and Read).
8. Name it.
9. You can now use that permission level on your form library to allow users to create forms without having the risk of users modifying other people’s forms.

This is an easy steps list, if you need more information about how to administer permission levels go to here.

How to create or copy permission levels from programming

Create a “New” by Making a Copy of Existing Permission Level