Lowell (7/30/2013)
i have a big proof of concept CLR project that is filled with items i either create myself, or find here on SSC.I just keep adding to it as I encounter ideas.
some of the things I've done in it:
Regular Expressions.
Read Write Files and Folders, including binary/blobs.
Send Email.
Read Email via POP3.
Read Email via IMAP.
PGP Encryption/Decryption.
AES Encryption/Decryption
Zip/Unzip Files.
Send/Get files via FTP and SFTP.
Convert RTF to text/text to RTF/HTML to RTF.
Export a table or query to multiple formats via a web service.(excel/word/pdf/mht/html/more)
A different write to PDF function.
Read Excel without Office DLL's.
HTML Encode/Decode functions, UrlEncode/Decode Functions.
Those are some pretty good ideas for CLR. On the one for reading/writing files, did you check to make sure that any parameters passed to them were "DOS Injection" proof?
The usual caveat here applies, just because it can be done in TSQL, or CLR, does not mean it's
the right thing to dothe right place to do it.
Fully agreed but you also have to remember something else. Different companies and organizations (the Department of Defense, for example) have different rules/restrictions/availabiliuty on what can be used and you can't always use the "right place" to do it but the job must still be done.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)