sql table vs sharepoint list

Question

_{Monday, May 28, 2012 3:59 AM}











Hi,

I would like to understand the factors we should consider for deciding whether to go for sharepoint list or sql tables.

I have already gone through below link:

http://msdn.microsoft.com/en-us/library/ff647105.aspx

Thanks, Nilesh

All replies (3)

_{Monday, May 28, 2012 4:33 AM ✅Answered | 3 votes}

Hi Nilesh,

Developer whether they should use SharePoint lists or database tables to hold the data for his application

It depends on as many factors into account as possible.
1)Who will be maintaining the data? 
2)Will the data only be used in your SharePoint application or does it need to be available across the enterprise and used by a multitude of systems?
3)What standards are already in place for application data?
4)Are there security concerns for this data?

All of these questions and more need to be answered in order to decide where you should store your data

As you read in above msdn site Sharepoint list and storing of data in database has its own advantages it depends upon developers choice as I described below .

SharePoint lists consist of rows and columns that store data in a similar fashion to a traditional relational database management system such as SQL Server. However, a benefit of lists is that SharePoint includes Web Parts that provide simple methods for managing the data. If the data was stored in a database, it would require custom user interface components to access it and manipulate it. Also, specialized skills are required to design, implement, and maintain a custom database. Another advantage of using lists is that custom workflow and event handlers can easily be registered to them.

There are also advantages to storing data inside of a database. One is the availability of all the ACID (Atomic, Consistent, Isolated and Durable) properties of transactions. If your business logic requires transactions, storing data in a database is preferable to using lists. Also, SharePoint lists are meant to store simple data structures. If you require a complex data model with intricate relationships, a database is more appropriate. The Training Management application has three data storage requirements. It stores data related to training courses, registrations, and registration approval tasks. All the data is relatively simple and does not use transactions. The registration data also requires that there be a workflow. All these reasons make SharePoint lists the appropriate choice

The following table summarizes the benefits of using databases and SharePoint lists.

Basweshver Jewale

_{Monday, May 28, 2012 5:25 AM}

Hi Nilesh,

The only factor that decides whether to go for SharePoint List or SQL tables is the "Requirement". The SharePoint gives more flexibility to use lists with Workflows, Web Parts, and over all the security. Use of sql is depends on the requirement, like you have to manipulate some complex calculations and have custom development with the business logic to be handled on database layer.

As per my little knowledge, we should try to stick with using SharePoint Lists for storing data.

Regards

Please remember to click "Mark As Answer" if a post solves your problem or "Vote As Helpful" if it was useful. It'll help other users who are visiting your thread for the similar problem.

_{Tuesday, May 29, 2012 6:02 AM}

for which part of document you need further explanation?