I have tried to delete the primary log file and it does, indeed, yield an error. What I'm actually trying to accomplish is to proactively detertmine which log files are dropable and clean them up. I could give you the details of how I came to be in this situation but its a long, incredibly boring story. It suffices to say that the main log file is no longer considered the primary and the "temporary" additional log file (on another disk drive) has become the primary. I believe that this happened when the database was restored to a new server location. This particular entanglement I have resolved. Moving forward, I have an administrative task which looks for and removes "temporary" log files. It made the erroneous assumption that the primary log file would be on the designated Log drive. I'd like to alter the logic to explicitly exclude the "primary" log file but I can't find documentation on how to determine the "primary" attribute.
Too often we enjoy the comfort of opinion without the discomfort of thought. - John F. Kennedy