Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Architect the relational db

  Asked By: Ladonna    Date: Sep 22    Category: MOSS    Views: 741

My team currently need to design a leave application solution for a
client using MOSS 2007. The thinking was to create a relational sql
server database with referential integrity constraints and represent
the data and business rules in sharepoint via custom aspx pages.
Would you recommend using sharepoint lists and content types (with
custom C#) or is it better to build line-of-business functions into a
seperate sql database with custom aspx.
I cannot find any whitepapers to help us make the decision

Share: 

 

1 Answer Found

 
Answer #1    Answered By: Malcolm Maxwell     Answered On: Sep 22

SharePoint lists are not relational  and don't support referential integrity
contstraints. If those are requirements of your application  you should put the
data in a relational database like SQL or Oracle. The only thing I would
suggest doing differently than what you suggest would be to write your
application as a set of custom Web part components rather than custom ASPX
pages. The code is very similar, but web parts are more flexible, fit into the
SharePoint environment better, and are re-usable.

 
Didn't find what you were looking for? Find more on Architect the relational db Or get search suggestion and latest updates.




Tagged: