We as software developers have a need to write logs so that our support department as well as ourselves have some information as to why some processes might not be working as expected. One standard moment to write to a log would be within a catch clause... now the SF generates (most of) our catch clauses, so the only way for us to log caught messages would be if Thinkwise provides us with a standard way of logging (which is called from the generated catch clauses by default). But of course we also need to be able to call the log procedure ourselves. The most important thing to factor in here is that most issues get rolled back, undoing any logging in the process if not implemented correctly.
I'm thinking of a procedure (something like dbo.tsf_write_log) which at least takes a message (nvarchar(max)), but maybe also other stuff, like procedure name or the likes of that. Of course things like a timestamp get added automatically by the logging procedure
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.