Turn on more accessible mode
Skip to main content
Turn off more accessible mode
New Zealand MS Communities
Sign In
|
New Zealand MS Communities
This Site
This List
Home
Events Calendar
Code Camps
About Us
Mailing Lists
Society Friends
Contact Us
**Tech.Ed Express Roadshow**
New Zealand MS Communities
>
SharePoint Discussions
>
What Shouldn't You Do With SharePoint
SharePoint Discussions
Quick Launch
View All Site Content
Surveys
UserGroupSurvey
Public Lists
Events Calendar
Job Vacancies
Community Resources
Resource Library
Resource Links
Blogs Links
User Group Presentations
SharePoint Conference Presentations
Reference Lists
NZ User Groups
Leaders Resources
Leaders Home Page
Leaders Site Guide
Tours
UGLeadSurvey
Modify settings and columns
Topics and discussions regarding the design, planning and usage of SharePoint in NZ organisations
Actions
View:
Flat
Posted By
Post
Posted: 11/03/2010 7:21 p.m.
View Properties
Reply
Anything that is commonly implemented with relational databases
complex data structures or relationships
highly transactional systems
SharePoint can often be the front-end for relational database data but shouldn't be the back-end
Show Quoted Messages
Posted: 11/03/2010 7:22 p.m.
View Properties
Reply
SharePoint won't shortcut the thinking that needs to go into any system design
Show Quoted Messages
Posted: 11/03/2010 7:25 p.m.
View Properties
Reply
Don't start custom development without understanding what is possible with the out-of-the-box (OOTB) functionality, web parts etc it might be unnecessary
Show Quoted Messages
Edited: 11/03/2010 8:12 p.m.
View Properties
Reply
Nicholas Hadlee
Panel Question: What Shouldn't You Do With SharePoint
What are the sorts of situations where SharePoint may not be the best solution/method of approaching the problem?