Probably not a real good idea but there's always the TSQL workaround:
EXECUTE xp_cmdshell 'DEL (...)'
If you're certain of the location of these .txt logs, this simple shotgun approach is easy.
That MSDOS command help looks like:
Deletes one or more files.
DEL [/P] [/F] [/S] [/Q] [/A[[:]attributes]] names
ERASE [/P] [/F] [/S] [/Q] [/A[[:]attributes]] names
names Specifies a list of one or more files or directories.
Wildcards may be used to delete multiple files. If a
directory is specified, all files within the directory
will be deleted.
/P Prompts for confirmation before deleting each file.
/F Force deleting of read-only files.
/S Delete specified files from all subdirectories.
/Q Quiet mode, do not ask if ok to delete on global wildcard
/A Selects files to delete based on attributes
attributes R Read-only files S System files
H Hidden files A Files ready for archiving
I Not content indexed Files L Reparse Points
- Prefix meaning not
If Command Extensions are enabled DEL and ERASE change as follows:
The display semantics of the /S switch are reversed in that it shows
you only the files that are deleted, not the ones it could not find.
How I see it is that use of BCP and other SQL utilities shouldn't be a big deal as long as this database isn't in production or online allowing general access rights.
You do understand that Maintenance Plan requires sysadmin rights?
Submit an article or tip