where to encrypt

[BigMag]

Hi there,

Is it possible in a Stored Procedure to call a module which can encrypt my data and insert/update/delete/select this encrypted data into/from the table?


what kind of probems can I encounter?
Is this secure?
Can I use a c- or pascal interface?

Thanks in advance


M.
BigMag, The Netherlands.
someone@euronet.nl (no kidding!)

 

[tlbroadbent]

Check the FAQ at

http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14035.

Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.

 

[BigMag]

Tlbroadbent,

Thank you for your response, it not really answered my questions.

I want the security of the data to be completely into my own hands. For that I have a module which encrypts data (a few thousends bits), written in a 3GL language, and runs with a c- or pascal interface.

So where can call this module, so the data is encrypted in the tables? And is the method secure?

BigMag, The Netherlands.
someone@euronet.nl (no kidding!)

 

[tlbroadbent]

There is no way to directly call your 3GL language from a SQL procedure. The article in the FAQ points out that you can develop an extended stored procedure (XP) which is esentially a DLL. Of course, you could write the DLL in C.

There are other ways to run your code. For example, you could use xp_cmdshell to run the program but the interface is not very clean and probably not as secure as you want. Check the following link if you are interested.

How can I run an external (non-SQL) program/dll etc. from within a TSQL SQL Server script?

http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14146

I believe that your best option would be to encrypt your data in your own application and then send it to SQL Server. This process could be made very secure. Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.

 

[BigMag]

The program is in cobol and compiled to a DLL and has a normal I/O interface. I know it can be dynamicly called from any platform which can make calls to modules with a c- or pascal interface.

So it must be possible to dynamicly call this DLL in an extended Stored Procedure, the same as a pascal module can be called?

Is it also possible to consider this XP as a normal module, with interface, which can be dynamicly called from several stored procedures?

M. BigMag, The Netherlands.
someone@euronet.nl (no kidding!)

 

[tlbroadbent]

I'm unfamiliar with all the mechanics of creating DLLs and XPs. I don't know if the limitations imposed by SQL Server will prevent you from doing what you want. Someone else will have to advise. Once you create an XP, you should be able to call it from any T-SQL script or procedure. Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.