We have an application built on top of a SQL Server 2005 that we have no control. We recently discovered that this application is sending some very inefficient SELECT queries to SQL which is causing the issues with serious capabilities on the database. I know that to open the application for the right solution is to open the code and to change the questions, but for reasons I will not go that time that I will take a long time. Is there any way that we can block this specific query on the SQL server and choose to do something else optimal?
You can use this approach, it works like a magic for me :) < / P>
Instead of trying to intercept and modify the Ascoll calls coming from the Apple, you can apply an abstract layer without changing the application SQL instead. For example, if you can modify the DSN or login connection string for the application, then insert the following. Suppose the current database is [A]. Create a new database [B] in which [A] contains ideas and functions (but not table) with the same name, then modify them in the context of tables in [A]. Whatever your add (to which I'm assuming) implementing row-based security, filtering etc. I again, modify the application DSN to use the database [B] instead of [A].
Comments
Post a Comment