Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Intercept SQL server request

Author  Topic 

jwise
Starting Member

3 Posts

Posted - 2008-07-09 : 13:26:37
Hello,

I want to intercept the requests that come to MS/SQL server from .Net clients. I will analyze these requests and determine if the request is "for SQL" or "for my custom code". If it is "for SQL", I wish to pass this request on to MS/SQL and have it processed normally. If case (2), then I wish to forward this request to my custom code. This code will essentually emulate SQL server with data from other sources. The goal is to insure the client code is totally unaware of where the request was processed.

Does this make sense? Is it doable? Are there performance issues with this strategy? In case you're wondering, this idea comes from KB287932 (http://support.microsoft.com/kb/287932).

TIA

maninder
Posting Yak Master

100 Posts

Posted - 2008-07-09 : 16:17:09
you mean your system will act as a middleware between the DB and the Client.
you will have to write a custom server app, that will act as a middleware and process these requests. This will probably have to SHUT the server down to outside work and only talk/take requests from your middleware app. something not impossible, but you will surely have to spend months/years in designing one (according to me). Or Capture everything in a nicely Designed SQL Database and process the requests from there...

Maninder
SQL server Architect / Admin (DEV&PROD)
Go to Top of Page

jwise
Starting Member

3 Posts

Posted - 2008-07-09 : 16:47:05
Thanks for your reply.

You are correct in that I am trying to develop middleware. I certainly hope your scope estimate is wrong! Since I have zero experience writing this kind of code on Windows, I am in no position to debate the issue. If this were a mainframe, one would find the first SQL module that touches the request. This code would be renamed. A substitute module with the original name would make the decision. Not a big challenge at all... if you know the module name.
Go to Top of Page
   

- Advertisement -