[AccessD] !RE: Database vs Sharepoint

Eric Barro ebarro at roadrunner.com
Fri Jan 8 20:12:04 CST 2010


Jim,

Even the workflow management aspect doesn't really offer much. You will need
either Sharepoint Designer or Visual Studio to design workflow that has even
the slightest complicated logic. I won't even go to the convoluted way it
uses lookup logic. :)

Eric 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Friday, January 08, 2010 7:34 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] !RE: Database vs Sharepoint

John,

<<Abstraction always comes at a price.>>

  Excellent point.  SharePoint is a fantastic tool for what it was designed
to do; workflow management and collaboration.  But to try and use it as a
database?  No, definitely not.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Friday, January 08, 2010 10:02 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] !RE: Database vs Sharepoint

 >   My somewhat subtle point there was that "slow" is a relative term.

LOL.  I didn't find it all that subtle!  ;)

And yes, if you look at what they are doing (sharepoint), using a SQL Server
to hold denormalized data and then normalize / denormalize on the fly, it is
never going to be in the same league as a true database.

It is amusing that in the original post a "sharepoint expert" (not a
database expert is implied
here) is "pronouncing" that sharepoint is much better than a true database,
when sharepoint is in fact built inside of a true database.

So much for "expert".

And again, the point has to be "better than what FOR what?".  It seems to me
(and I am speaking from immense ignorance) that Sharepoint is attempting to
abstract away the complexities of a true database so that the "average" user
can use a database without having to know how to use a database.

Abstraction always comes at a price.

John W. Colby
www.ColbyConsulting.com


Jim Dettman wrote:
>   My somewhat subtle point there was that "slow" is a relative term.  
> In some cases, it depends on how much hardware you throw at something.
> 
>   Look at Vista.  Folks that bought a brand new PC thought it was OK, 
> but the 90% of us that tried it without buying something new found it
"slow"
and
> not all that great.
> 
>   My guess would be that as part of a University, your pretty heavy on 
> hardware (at least more so then most data centers).  Most SharePoint
setups
> I've seen are always done with one or two servers at best.
>   
> 
> Jim. 

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list