SharePoint4us

Advantages of using stored procedures

You can create the procedure once, store it in the database, and call it any number of times in your program. 

If the operation requires a large amount of SQL code is performed repetitively, stored procedures can be faster. They are parsed and optimized when they are first executed, and a compiled version of the stored procedure remains in memory cache for later use. This means the stored procedure does not need to be reparsed and reoptimized with each use resulting in much faster execution times. 

An operation requiring hundreds of lines of Transact-SQL code can be performed through a single statement that executes the code in a procedure, rather than by sending hundreds of lines of code over the network.

Users can be granted permission to execute a stored procedure even if they do not have permission to execute the procedure's statements directly.

In SQL we are having different types of stored procedures are there

System Stored Procedures:

System stored procedures are stored in the master database and these are starts with a sp_ prefix. These procedures can be used to perform variety of tasks to support sql server functions for external application calls in the system tables 

Ex: sp_helptext [StoredProcedure_Name]

User Defined Stored Procedures:

User Defined stored procedures are usually stored in a user database and are typically designed to complete the tasks in the user database. While coding these procedures don’t use sp_ prefix because if we use the sp_ prefix first it will check master database then it comes to user defined database

Extended Stored Procedures:

Extended stored procedures are the procedures that call functions from DLL files. Now a day’s extended stored procedures are depreciated for that reason it would be better to avoid using of Extended Stored procedures. 


Hope this blog helps you..... 

What is the Purpose of it ?

Introduced in SharePoint 2010

How to Configure the Content Type Hub?

Let us see, how to use the content type hub in SharePoint 2013.

Let us see that with step by step procedures.

1. Let us create our SiteCollection for the Content Type Hub

                                        Create Site Collection

Once its created, Click on Site SettingsàManage Site Collection Features.

Activate Content Type Syndication Hub feature

You  can see the created Site Columns 

  Now Create a new content Type  add these Site Columns to It

   Add Existing Site Columns

Click on Manage publishing for this content type and Select Publish and click ok 

Note: This Link only gets enabled if we activate Content Type Syndication Feature.

Click it Manage publishing for this content type and Select Republish and click ok

Now go to Site Setting à Under Site Collection Administration àContent Type Publishing.

You can see the published content types here.

 If you are not able to see that immediately, there is a timer job which needs to run. This timer is configured as Hourly basis by default. We can execute this time manually also. The timer is “Content Type Subscriber”. 

Create new Site Collection or  Web Application   Goto Site Settings  Site Content Types

This is the way of Configuring the Content Hub

Below are some of the limitations/FAQ about content type hubs:


1. Which field types are supported? Custom fields and external data columns are not supported(you cannot create external data columns in the content type gallery).
 
2. What happens if a web application is member of two different Content Type Hubs? The default Managed Metadata Service(MMS) gets the priority and will be your content type hub. However, if you customize the service application associations for the web application, you can select the appropriate MMS application proxy for the content type hub.
3. What happens if a user changing a synchronized Content Type inside the Target Site Collection? The subscribed content types are marked 'read only' in the target site collection. Users are unable to manage/change the synchronized content types inside the target site collection. Changes to the content type should always be made in the content type hub and republihsed to push the changes to the subscribed sites.
4. What happens with content types within the sub-site structure? 
Content type subscription is a site collection level feature, so you consume the content types in the top root web and it flows down the sub-sites.
5. Are Workflows supported and if yes what are the limitations? Unfortunately workflows are not supported. However, once you have your content type published to the target site collection, you can create and associate workflows to the subscribed content types in the target site.
Update:  on associating workflows with published content types. As always, you are able to still create list workflows in the target site collection instead of associating with the content type if required.
 
6. What happens with document templates? Document templates associated with the content type are also published along with the subscribed content type.
 
7. What happens with Document Set content Types? Yes, you can subscribe to document set content types. In this case, all the dependent content types with the document set & the document set itself will be published to the target site. However, you should have the Document set feature activated in the target site.
8. What about feature dependencies? Feature dependencies are not activated automatically in the target site collection. Thus, they need to be activated manually before the subscription process, else the content type publishing job will fail in the target site collection for that subscribed content type. Best example is when you subscribe to document set content types
Thanks