Quote:
Originally Posted by cstreit
The transformations are too complex to reasonably do in SQL.
|
In the serial processes I alluded to (which were built in MS SQL Server) we use stored procedures... you can do some extremely complex transformations in there, essentially you can treat it as a programming environment hosted by the DB. Then when the transform for one step is done, trigger the next.
I have one system I architected this way which takes electronic debits from a banking platform, transforms them on a user basis into one transaction amount, looks up and decrypts the account information, builds a batch file on a remote drive and SFTPs it to a third party vendor and then follows up with a confirmation email... all 100% in SQL Server, including the scheduling.
__________________
Grant
In the stable: 1938 Buick Special model 41, 1963 Solex 2200, 1973 Vespa Primavera 125, 1974 Vespa Rally 200, 1986 VW Vanagon Syncro Westfalia, 1989 VW Doka Tristar, 1995 Toyota Land Cruiser, 2011 Pursuit 315 OS, 2022 Tesla Y
Gone but not forgotten: 1973 VW Beetle, 1989 Porsche 944, 2008 R56 Mini Cooper S
|