These are actually two different technologies. ActiveState provides an ActiveX scripting engine for Perl with their Windows distribution, called PerlScript. This allows you to use Perl in all the places that, for example, you can also use VBScript or JavaScript, including ASP, client-side web scripting (that is, if the client also has ActivePerl) and SQL Server Data Transformation Services.
I've used Perl(Script) quite successfully within SQL Server DTS and love it. It allows me to do all sorts of things that you can't easily do with the default VBScript, such as Perl regexes and SMTP email. The best part is being able to use modules off of CPAN, where with VBScript you'd normally have to find and install an appropriate COM object.
Now, SQL Server also implements extended stored procedures, such as xp_cmdshell, but my knowledge of them is somewhat limited. However, they sound similar to the Sybase versions. As far as I know, they can only currently be written in C/C++, and then should be compiled into a DLL.
My colleagues and I have discussed something like this idea before, but we're Perl coders with only vague experience with C++, so it's never gone past the concept stage. Our main desire was to have Perl regexes within Transact SQL, but it would be great to have the complete functionality of Perl at hand.
If you do develop a working way to call Perl from Sybase, please post the code, or explain how you've done it. It's quite possible it might also be applicable to SQL Server, due to its shared ancestry with Sybase.
-jehuni
In reply to Re: Perl in the database?
by jehuni
in thread Perl in the database?
by mpeppler
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |