There is also the cost of the database, and I would not suggest putting production data on SQL express, or windows internal database. (your choises are WID, SQL express, or $QL) Plus the cost of backing up that DB, and the proper set of the DB, Sharepoint can kill a DB server in a heartbeat if not setup properly.
Also, there is MS Search server express, I would suggest running it seperately from WSS, and its not needed if you go with full blown MOSS. But it gives you alot of the MOSS features scaled down a bit.
To really do sharepoint right, you really need to know C#, its a must, Now, you might be able to get away with out all that knowledge simply because of the smal user base, your code wont NEED to be as efficient as enterprise code does.
There are also a lot of 3rd party apps that make things easier, my personal suggestions, got to:
www.codeplex.com - search sharepoint
www.nintex.com - Drag and drop WYSIWYG Workflow design.
Alos, if you did go with sharepoint, I would try to get out of the access DB mantality, user WSS custome lists instead.
But the best Idea would be to piick several collaboration platforms and running a pilot with the actual users and ask them what they like.
Also, DO NOT USE anything older than WSS3.0 - There not point, WSS3 is free, MOSS 2007 is not free, and dont forget about the DB server you'll need.
Make sure if you bring in a SQL DBA that he/she has experiance with Sharepoint and SQL, its a totaly different world for them, there are things that you just dont do with Sharepoint DBs, that is normally part of the SQL DBA toolset.
Main Topics
Browse All Topics





by: DhopePosted on 2009-05-14 at 04:50:28ID: 24383791
1) I don't think it'd be OTT, and given a small company you'd be able to ensure a swift move to using it. Our environment is not large but has 400 users and some people love SharePoint, others still haven't a clue what it is so the uptake varies wildly.
om/en-us/w indowsserv er/sharepo int/ bb6844 53.aspx om/en-gb/w indowsserv er/sharepo int/ bb4007 55.aspx
m/en-us/sh arepointte chnology/ F X101758691 033.aspx
2) From a desktop point of view then Office 2007 would be better, but 2003 is adequate to allow people to modify lists in datasheet view, check documents in and out easily and to integrate tasks with Outlook etc.
SharePoint version 2? Would think WSS 3 would be fine - http://technet.microsoft.c
To see differences between SPS2 and WSS3 have a look at
http://technet.microsoft.c
4) Windows SharePoint Services (WSS) is free. Microsoft Office SharePoint Services (MOSS) isn't.
To see differences between WSS and MOSS have a look at
http://office.microsoft.co
5) It's fairly quick to get used to. I came from a desktop & server support background, knew enough about HTML, C# etc to be able to read what others had done but struggle to write things from scratch myself.
Because you have an understanding of DBs, some coding, some HTML, plus probably some desktop and server support then I don't think you'll struggle gettings things up and running.