Recieved a quick question from a fellow K2’er out there (Peter Yao) :
Q. How large of a SQL Server database have you seen this product scale out to? We are starting to using K2 SP4 now.
Answer : When implementing K2.NET, there is a “Data” and a “Log” database for managing the interaction of the various workflow steps, user tasks and activity data. However, this data is fairly small, not the sort of scenario that would cause SQL Server any troubles. Even the “hits” to the server would be fairly low, given that many workflow tasks can sometimes be measured in days and weeks – not needing sub-second response time – even with multiple users.
I’ll delve a bit more into the database/s that are installed with K2.NET – can use Reporting Services to pull out some stats/graphs, etc.
The most recent K2.NET solution I’ve delivered used a custom database for information about customers, names, addresses and all – with documents stored in Sharepoint. As such, the SQL Server scalability wasn’t so much of a concern. This custom database may have been Oracle, or DB/2 – and K2.NET would still be able to integrate, as long as “it’s own” database/s were within SQL Server.
In fact, I think you can even use SQL Server Express edition (will have to check on that one). But – must be Windows “Server” – can’t run the K2.NET server on Windows XP.
Of course, you can still develop workflows using Windows XP (K2.NET Studio). My current laptop runs Windows XP, and I use Virtual PC to have a Windows Server 2003 instance, with the K2.NET server, and SQL Server also.
So – the answer to the question is not K2.NET “scalability” with regard to SQL Server – but instead, the custom database that K2.NET will integrate to. And that’s unrelated to K2.NET (as such).