I didn't know it was considered improper (although intuitively, the thought did cross my mind), I was just asking because it seemed like a nice idea to know what options were out there.
(Also, I have to assume that there are probably those who for whatever reason simply don't have access to SSIS (or whatever proper tools you may think of in their particular case) and because of that have gratefully made do with a t-sql technique for sending an email, creating a text file etc - although I admit this isn't my case).
I guess I just thought it would be prudent to understand my options in at least some of these items. I do sometimes feel like it's overkill to create an entire SSIS package for the purpose of sending a couple emails, if I could use SQL Job Agent's "transact sql" type in the Step dialogue as opposed to creating an entire DTSX file, complete with its own overhead, storage, documentation, etc. I don't really see the security implication in this example, a sql job agent which is running either an SSIS package or a T-SQL statement, probably running either/both of them using an SA.
Anyway - not arguing with you just explaining that I wasn't planning on transferring all my beautiful ETL packages over to these techniques or anything like that, I just wanted to know about some of them. There are a few cases where I schedule a stored procedure, and the only real reason to use an ETL or other programming type of tool is to send mail based on if there is some new data, etc. It seems a little overkill to do this in SSIS if T-SQL is perfectly capable of doing the exact same thing and it's only a couple lines of code for a brief email.