Share Point Saturday India STORING LARGE DATA IN

Share. Point Saturday India STORING LARGE DATA IN SHAREPOINT Jackson Chackungal Aug 2012 August 2012

Disclaimer : Most of the information here is common sense or should be. . August 2012

Know your limits Threshold Boundary http: //technet. microsoft. com/enus/library/cc 262787. aspx Supported limit August 2012

Common sense - Don’t just look for how much you can put in, also consider what it is to be used for Image source http: //txbrowns. blogspot. in/2011/02/monstertruck. html August 2012

So you know the functionality, what’s next ? August 2012

Lets go back to the basics … August 2012

Meant for Collaboration Version-able Flexible ‘The List’ CRUD operations are just there Open Customizable August 2012

A List IS NOT a replacement for a Database table… IS NOT!! Should I be using a list or a database is not a discussion you should be having… Its do I need a structured backend for my application or do I need a lightweight repository August 2012

You could try the best of both worlds – Use external content types However…. August 2012

Scenario – how things go from good to bad to ugly August 2012

The requirement – An Issue tracking system � � � � Assign issue, update issue One person should not be able to update another user’s task Tasks required for multiple departments One department should not view other department’s tasks Users are not satisfied with the list view, they want to view tasks in a fancy grid view with ability to update status of multiple issues in one shot Certain issues for a department are marked as sensitive – only users related to the issue should be able to view it Report of all open issues , issues open for more than x days, trend of issue closure across last quarter August 2012

The requirement – An Issue tracking system � � � � Assign issue, update issue One person should not be able to update another user’s task Tasks required for multiple departments One department should not view other department’s tasks Users are not satisfied with the list view, they want to view tasks in a fancy grid view with ability to update status of multiple issues in one shot Certain issues for a department are marked as sensitive – only users related to the issue should be able to view it Report of all open issues , issues open for more than x days, trend of issue closure across last quarter August 2012

The requirement – An Issue tracking system � � � � Assign issue, update issue One person should not be able to update another user’s task Tasks required for multiple departments One department should not view other department’s ems t i e tasksy to hidviews, Have y tr e of / t ou rea ’ s n s t d the Users not satisfied with the list view, they to c d Do ing u are o e c u r mentat want i e r d k e e n on be practic toioupdate ma intasks g r s in inca view grid view with ability. Thfancy y b e c t s t f a or Fine st pl scrip spx e eans an P e r mission Graine c a status in one shot r m tion issues s in Sh d m. a multiple e jav iteof I h f are. Poi not Bin t a o t m i r n y t? ed manissues Tmarked And Re oday ! g it. as info Certain for a department are e e a d , r it. a th d – OM ch s–seonly i S h C sensitive users related to the issue should be , w e acc rvices e b view able to. bse etcit e W rch a Report. Seof all open issues , issues open for more than x days, trend of issue closure across last quarter August 2012

The requirement – An Issue tracking system � � � � Assign issue, update issue One person should not be able to update another user’s task Tasks required for multiple departments One department should not view other department’s tasks Users are not satisfied with the list view, they want to view tasks in a fancy grid view with ability to update status of multiple issues in one shot Certain issues for a department are marked as sensitive – only users related to the issue should be able to view it Report of all open issues , issues open for more than x days, trend of issue closure across last quarter August 2012

Large List considerations � Try to use the default thresholds as far as possible � Use content types for basic categorization of content � Consider the usage of indexes � Leverage Metadata navigation � Split information using folders – better for navigation and performance August 2012

Ways to access data in lists � Various – List View, CQWP , CAML queries etc. . � and Search August 2012

The age old debate …. Site Collection vs Subsites August 2012

How do I usually go about it ? http: //jacksonc. wordpress. com/site-structure -web-apps-vs-site-collections-vs-subsites/ August 2012

Lets talk about documents… August 2012

Size Matters August 2012

Know your limits http: //technet. microsoft. com/enus/library/cc 262787. aspx August 2012

Plan your file storage strategy based on type of document and usage � Types of documents � Usage � Project related � Collaborative � Legal – scanned in � Read only � Media files � Linked to by external apps � Archived files � Record – rarely used � Application files � Accessed by other apps �… �… Don’t just plan on dumping everything into Share. Point August 2012

In Conclusion We need a plan of attack! I have a plan: attack! Not a good idea August 2012

THANK YOU !! August 2012