RE: newbie - lists vs. database

Thanks for the response Wei

My question is more related to best practice than what is possible.

What is best practice when designing a new application from scratch? Is it
to create a database (using SQL Server) or to let SP handle this for me by
customizing lists as needed. I can duplicate trigger functionality with
workflows - right? I assume SP handles indexing within the lists to expedite
search functions.

Also, what is best practice for creating data entry screens when writing a
SP web application? Should I just use the edit in dataheet functionality or
InfoPath or web forms or something else?

Thanks for your help.

-Rob

"Wei Lu [MSFT]" wrote:

Hello Rob,

I understand that you want to know some difference between Sharepoint List
and Database.

Well, generally speaking, Sharepoint List is only a Layout layer and it get
the data from the Sharepoint backend databases.

You could use the Office 2007 products like Excel 2007 and Access 2007 to
connect with the Sharepoint list directly. So for your first question, if
you are using Access 2007 or Excel 2007, you could link to Sharepoint List
and use the Office client product as a front-end.

For your second question, I am not sure what database you are using. Take
SQL Server for example, you could add index and trigger in the database to
get more funcationality.

But if you only need to get the information from the sharepoint list, you
could use the list instead.

Hope this helps.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights
.

Relevant Pages

  • Re: Reports in OLTP system
    ... I wonder what is a usual practice of serving aggregate data in ... By aggregate data I mean for example monthly sales summary. ... Triggers not so good. ... Java object-relational mapping framework that "simplifies database ...
    (comp.databases.oracle.misc)
  • Re: One or many DataSet
    ... > Is it best practice to keep the amount of DataSets small but with many ... dataset is not a database, and it shouldn't be abused as one either. ... > Table2 has 2 columns, CustomerID and OrderID ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: ASP Classic - Alphabetical lists
    ... Select * is bad practice. ... So, this puts a lot of strain on the database, as well as spiking the ... provided that the programmer knows his stuff, ... So the extra strain in these circumstances will be minimal. ...
    (microsoft.public.inetserver.asp.general)
  • Re: Autoupdate field with number of related registers
    ... In my setup, as long as a school is not giving a student ID by ... I give an ID that has no meaning too. ... Just with a tiny change of the setup of the database, ... In practice school data contain many faulty information or some pupils ...
    (comp.databases.filemaker)
  • Re: Customer asks for database password & link in
    ... customer, instead say "That will cost you an additional $$$ for the ... additional functionality", or "We cannot do exactly what you have requested, ... Your license to them must have a limitation on what they can do with your ... > one of my programs which holds a large database. ...
    (microsoft.public.vb.general.discussion)