Imagine my glee when reading this thread after a long day of trying to get a simple answer as to where to deploy a JAR / where data should be landed. 7 hours l

Imagine my glee when reading this thread after a long day of trying to get a simple answer as to where to deploy a JAR / where data should be landed. 7 hours later, 4 email chains and around 12 people involved, and still no answer, and they've all gone home... I've been working in a project for an insurance conglomerate for the past 6 months (total project has been running close to a year) that has very recently hit the rocks. The client has gotten fed up of our inability to deliver, so canned the long term plans of the project in favour of a stop gap solution in order to fulfil some short-term business goal. We've acquired a relatively ludicrous amount of hardware (i'm talking $100,000+) for what is essentially the equivalent of SELECT COUNT(*) FROM ALL TABLES, which is then filtered into some slow, unusable BI tool that costs $999+ per user / per year. The real tragedy is they already have geo-diverse SQLServer instances running that would have allowed them to do this in 1 evening. 1 year and $1m+ in billable's and we somehow are going to fail to deliver even that.