All you need is a case statement to fire the correct code going forward.
It really sucks to bring in another back end but the customer must pay for what THEY WANT.
You could really consider putting up an AWS cloud environment and getting your data from there. Or Azure. Now you get a little bit of redundancy going forward.
On Thu, Feb 28, 2019 at 3:42 PM mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
On 2019-02-28 09:45, Stephen Russell wrote:
I have some long stored procedures that are in the 3000 lines long arena
Jesus...that makes my head hurt just thinking about that. I get the efficiency angle but I really enjoy breaking work up into much more manageable/readable units in the DataObject code; plus, my approach means I'm not stuck with SQL Server in case I want to switch out the backends. There's varying schools of thought on that, and of course, pros and cons to each. I recall somebody (Ted?) saying something years ago about treating that backend as just big dumb iron in the n-tier system approach, which is what I use.
[excessive quoting removed by server]