<div>
If what you are trying to do could be done, it would blow security wide open. Anyone could change SQL statements on the fly and do horrendous damage or fraud. Therefore it's unlikely, though knowing Microsoft, not necessarily impossible.<br />
<br />
Some of the system stored procedures do more than a standard stored procedure, and use DLLs to implement themselves. They're not just a bunch of T-SQL statements lieke we would write.<br />
<br />
I think you'll have to look for another method.
</div>


<div>
I concur with crescendo. SQL Server is designed to be extensible, but not mutable -- in other words, they've intentionally tried to design it so that you can't change system components, including system extended stored procedures. Unless someone from the SQL Server development team weighs in on this and says otherwise, I don't think you'll succeed with this. :(<br />

</div>


<div>
Just as a friendly reminder: &nbsp;You will find experts more responsive if you take the time to maintain your open questions. &nbsp;You have asked 7 questions, &nbsp;3 have been subsequently deleted, 1 force accepted and 3 are still open. &nbsp;Here are all your open questions:<br />
<br />
1 05/12/2004 500 Server Error 415 with HttpWebRequest &nbsp;Open Internet Information Server <br />
2 09/12/2003 250 IFRAME takes about 10-20 sec to load, ma... &nbsp;Open Active Server Pages (ASP) <br />
3 08/03/2004 500 Microsoft SQL System Extendend Stored Pr... &nbsp;Open Microsoft SQL Server <br />
<br />
As you can see one of the questions is nearly a year old. &nbsp;It your choice, but also your responsibility.<br />
<br />
Let us know.
</div>


<div>
I think you should do it and post your results.....<br />
<br />
Do you have any idea how much you could screw up???? &nbsp;Not to mention if service packs come out and recreate the proc you replaced--then you have to move your proc back...<br />
<br />
What's the end result you're looking for? &nbsp;Maybe there are other ways...
</div>


<div>
could you share what is your goal. What would you like this procedure to do.<br />
<br />
-- cheers
</div>


<div>
Do you need any help maintaining your old open questions? 
</div>


<div>
&lt;&lt;I have tried many ideas, and so far this is the best looking one&gt;&gt;<br />
<br />
Don't mean to be rude, but the others must have looked bad...<br />
<br />
Are you sure that there's no way you can configure Sharepoint to do what you want? Messing with an application's SQL in a covert way seems destined to failure, doom and destruction. Tell us more about the Sharepoint stuff.
</div>


<div>
crescendo- &nbsp;your right. &nbsp;The other ways cannot be successful. &nbsp;At every turn, this microsoft product has many unconfigurable areas. &nbsp;Ultimately, I am trying to meet a very important requirement where we need item level permissions on documents in sharepoint, but sharepoint only allows per document library permissions. &nbsp;A solution is to have a separate document library for each file. &nbsp;At this point it seems like the only possible way to accomplish this, but the problem lies in a clean and cohesive UI. &nbsp;I am attacking the problem from the back-end. &nbsp;As far as the EULA, Im not worried, internal use only, and I have spoken with some Microsoft reps that said it shouldn't be an issue. &nbsp;I think that if you buy the license, you can do whatever you want with it, just can't distribute. -separate discussion though.<br />
The only other way I can see to get around this is by modifying the dll itself, and change the code which generates this sql string. &nbsp;Issue there is its assembly language, MSIL, and I dont have 4 months to become a novice hack at it, and further doesn't necessarily guarantee that I would be hacking the right dll in the first place. &nbsp;The applications organization is spread out between managed code, unmanaged code, SQL, XML, script language... very convoluted, very disappointing.<br />
<br />
So - Item level permissions in sharepoint is really my issue, so that goes beyond the scope here, but my idea for a solution rests in SQL. &nbsp;Any other comments are appreciated.
</div>


<div>
bowser17:<br />
<br />
Have you tried the following site? It needs a login, but the contents page seems to address exactly what you are looking for:<br />
<br />
<a href="http://msd2d.com/Tip_view.aspx?section=Exchange&category=Workflow" rel="ugc">http://msd2d.com/Tip_view.aspx?section=Exchange&category=Workflow</a><br />
<br />

</div>


<div>
Yes, I've searched high and low. &nbsp;Alot of content that is on that site pertains to Sharepoint 2001. &nbsp;If I haven't mentioned it earlier, we are using Sharepoint 2003. &nbsp;Other idea is: &nbsp;can you create a network filter that sits in front of SQL? &nbsp;Basically try to catch network traffic to SQL and modify it? &nbsp;Yes, I know, security....
</div>


<div>
Worded very nicely crescendo :)
</div>


<div>
We are all aware of this. &nbsp;I knew that the answer probably wasn't what I was hoping for, but I had to try!
</div>


<div>
<div class="content wysiwyg-content">
Hello-<br />
<br />
I want to modifiy a SQL statement that is being executed on the SQL server. &nbsp;It is being generated from what I can tell, a dll (Sharepoint), so I cannot modify it directly. &nbsp;My idea was to rename the sp_executesql and then add a new xp with the same name. &nbsp;That way the dll would call my custom version, which would modify the sql statement and the call the original but renamed version to get the results<br />
<br />
After renaming sp_executesql to sp_executesql2, the ext sp, it says ODBC: Msg 0, Level 16, State 1<br />
Cannot load the DLL (server internal), or one of the DLLs it references. Reason: 126(The specified module could not be found.).<br />
<br />
Additionally, it seems that if i just delete the original, and add my custom xp using the same name, sp_executesql, whatever the dll is doesn't do anything and the original behavior is restored.<br />
<br />
I am working on a Virtual PC so I dont complete screw up existing development dbs. &nbsp;SQL Server 2000.<br />
<br />
Thanks in advance.
</div>
</div>


Hello-

I want to modifiy a SQL statement that is being executed on the SQL server.  It is being generated from what I can tell, a dll (Sharepoint), so I cannot modify it directly.  My idea was to rename the sp_executesql and then add a new xp with the same name.  That way the dll would call my custom version, which would modify the sql statement and the call the original but renamed version to get the results

After renaming sp_executesql to sp_executesql2, the ext sp, it says ODBC: Msg 0, Level 16, State 1
Cannot load the DLL (server internal), or one of the DLLs it references. Reason: 126(The specified module could not be found.).

Additionally, it seems that if i just delete the original, and add my custom xp using the same name, sp_executesql, whatever the dll is doesn't do anything and the original behavior is restored.

I am working on a Virtual PC so I dont complete screw up existing development dbs.  SQL Server 2000.

Thanks in advance.

Microsoft SQL System Extendend Stored Procedure Overwrite sp_executesql

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.