SQL Server 2008 R2 StreamInsight | The Coffeehouse

LordNikon

http://www.microsoft.com/sqlserver/2008/en/us/R2-complex-event.aspx#Process

This looks like some very cool technology. What I'm wondering is if it is intended in part to enter the data historian market as a direct competitor, or is it intended to build on top of other data historians to bring more efficient and effective BI capability to the table. I suppose its success in that market will in some part depend on the emergence of various DCS/SCADA adapters.

I think this is big news and represents a huge market opportunity for partners.

Sabot
My name is Dave Oliver. I'm a Technical Architect.

Agreed it does look like some very cool technology .... 2008 R2 is going to be awesone!

staceyw
Before C# there was darkness...

imo, it seems it is more a general Pub/Sub system that allows you to subscribe to events using Linq queries (1 thing I have wanted, very cool). Publishers can be devices or other (triggers, etc). You can use this arch to subscribe to topics and publish some event that may be gathered from many sources (tables, static data, device input, etc). My first thoughts where things like realtime Dashboards and Twitter w/ Track and "realtime" push. Not sure.

KosherCoder

It sure looks like it could function in the process industry as a data historian. With .net integration, and even more significant the BI toolset MS provides, this could really become a huge player. The tools offered by the current market are far behind the times, unintuitive, and look unprofessional.

The Manufacturing Toolkit also opens up intruiging opportunities in this space.

Looking forward to Microsoft's offering!

staceyw
Before C# there was darkness...

In reply to KosherCoder

#Oct 5th @ 11:17 AM

Just curious. How would data historian be implemented as Pub/Sub? Does not sql change tracking and/or triggers allow this solution already for data history? What is the senerio you are thinking about? tia

LordNikon

In reply to staceyw

#Oct 5th @ 4:10 PM

Regular SQL is not fast enough and lacks optimal data structures to handle the data. Manufacturing execution systems, realtime monitoring of digital control systems & SCADA, monitoring the power grid, smart meters, oil & gas, petrochem, process manufacturing, all of these areas where you have intricate processes and digital controls generating a large amount of data in real time. StreamInsight lets you work with the event streams without having to necessarily worry about the underlying storage mechanism or latency. You can perform computations incrementally, in near real time, to do analysis without having to, for example, calculate an aggregate over 2 billion events. There are a number of established players who have the data storage piece down, and who "want" to be able to serve the analysis / BI needs on top of it. They have their own ways of providing for the incremental calculation. Mostly they aren't that great because there hasn't been enough competition to drive a lot of innovation. StreamInsight + the BI stack will fill a huge need in the market for which there is a lot of demand. Maybe I'm just a geek but if this performs well it is going to be a really neat piece of kit and crack open a lot of opportunities.

Microsoft Manufacturing Home

Microsoft Power and Utilities Blog

staceyw
Before C# there was darkness...

In reply to LordNikon

#Oct 5th @ 6:59 PM

I get the real time stream part and be able to sniff stuff out of the stream and do stuff. What I don't understand is the "data historian" part. If your archiving data, you need to make a Write. You can cache it, in a 24 hour stream, your writes still have to keep up. Are they talking about historian in terms of saving device stream output to DB or historian in terms of archiving DB changes?