I am curious what other people have done to implement read-only routing for a large number of procedures. Basically figuring out when to call procedures that are read-only with read-only intent.We have a user application that passes an encrypted string to a web service that directs it to our SQL Servers. I've been tasked with finding a way to make this happen without changing the application. The only thing I have been able to come up with is writing something (which I did) that will identify whether something is read-only or not and storing a big list.Then having the web service look up the given procedure and adding the intent where needed. I really hate the idea of calling SQL to figure out how to call SQL. It just seems backwards to me.Anyone have any better ideas or approaches?Thank you,Josh
↧