According to what I have studied about RBS so far, I've found that we can't just write an RBS provider that'll work with all ASP.NET applications as applications must be written to support RBS. While most of out clients are not ready to change their application
code, we were thinking if we can build a solution that just requires a web.config level change and it starts working.
Initially, we were thinking of writing an ADO.NET custom provider that will intercept all calls to database on its way and parse the sql statements and also change it fetch rbsid as well. But that seems to hurt the performance a lot besides we can't do anything
if command type is stored procedure.
So just wanted to check with you guys that is it safe to say that "Client applications must be written as RBS-aware applications to use RBS"?