We have an internal application which when viewing the events through Profiler, I see a bunch of ODBC Stored Procedures. Basic sequence is create proc as.... and then the execute then it deletes the same procedure. The server is showing a bunch of compiles and my guess is these ODBC stored procedures are causing that. The naming convention on these procedures is #odbc#userid. The developer that I have been working with on this found a MS article Q115907 in reference to this but, that article states that the user would have to have create proc permissions in order for this to occur. The user definitely does not have that permission.
Has anyone seen this and if so, how do you fix this?
I am working with the development staff to actually create stored procedures for the updates, inserts and deletes that are needed but, that will take some time for them to go through all their code so, I was looking for a quick fix. I do know that this will be the true fix.
Ultimately, this is not overly problematic, just seems like bad practice to me.
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot