This question is a little challenging to approach because by using the established term “data warehouse” you somewhat frame the question since that term includes the ecosystem of tools and processes that have built up around the enterprise of data warehousing. There are business intelligence questions that existing warehouse technologies are good at answering and others not so much. They are good at slicing/dicing/aggregating properties and displaying them. They are not so good at questions involving relationships – things like, what happens if product ingredient X is unavailable. If you have both types of problems then maybe you shouldn’t look at this a Microsoft vs Neo4j but look to Neo4j to solve some of the problems the warehouse isn’t solving.
-Paul From: [email protected] [mailto:[email protected]] On Behalf Of Chase Willden Sent: Tuesday, October 11, 2016 12:33 PM To: Neo4j Subject: [Neo4j] Neo4j as a Data Warehouse I'm struggling with an answer to this question. With very robust tools released by Microsoft for data warehousing, what advantages are there in implementing a graph data warehouse verses a traditional data warehouse with Sql Server? -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. ________________________________ -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
