How to route non-HTTP (MS SQL) traffic to a single VIP and then forward to different pools

A question concerning how to send MSSQL (i.e. Non HTTP) traffic to a single Virtual Server and then inspect and forward to different Pools. Clearly, if the incoming traffic could accommodate the HTTP profile, then conceptually subsequent pool routing is straightforward.For example, concatenate the domain name with a database specific URI, inspect the URI via a Traffic Policy or iRule and then forward to the associated pool.

 

However, in this case, the use of the HTTP profile to enable URI inspection is not possible. The incoming traffic is MS SQL and is associated with multiple databases. For a given MSSQL database, a WebApp tool called "SQL Server Management Studio" (SSMS) sends traffic to a single shared VIP. In order to avoid consuming scarce internal IPs I would like to use a single shared VIP for incoming MSSQL database traffic

 

Is there any technique whereby I could inspect an attribute asscociated with the MSSSQL traffic, and then forward to the associated database pool?

 

Much appreciated

 

Alex