Again a newbie question, so forgive it on the general forum, but you veterans are a good place to start I hope!

We are a very SharePoint focused organisation but we have several other LOB SQL systems that we want to hook into and write back to hence buying K2. Our interaction with LOB systems can wait ... but there is a lot we can do with it in the short term.

But I am up against a wall at the moment when someone asks for a fairly simple KT solution (ie: smartforms/workflow) in regard to whether I build this on a SharePoint list as the data source or I use the inbuilt K2 Database source and create the smart object from there instead.

My instinct is to use SP as the data source as we can visualise the data captured very easliy in house (infact any SP power user can untilize it and filter etc on the data views and create what views they need, they can roll it up across sites and use it as dashboards using external tools such as Lightning tools).  If I use a K2 database source as the smart object we are reliant on a professional SQL expert to extract that into a sequal report (potentially delivered on a SP Page). I actually have no idea what the sequal reporting bit means in all honesty.

But My question in essence is, what does using a K2 inbuilt database as a samrt object have 'over' using a a SharePoint list.  I understand the difference between a flat database which a SharePoint List is (ie: each item can't talk to each other).  Is that the advantage of using K2 as a data siource? .. is it a relational database, can each item see the other or am I am completely off mark with this?

Confuzled at K2.com :-)   Julie