|
Version:
3.3.0.0
6/15/2007
|
|
|
Download Setup
|
| New Features | |
Data-driven @sender_email parameter
It's now possible to use <sql></sql> structure to populate @sender_email parameter with data from the database. It's also possible to use {FieldName} construct when doing a mail-merge from a database query.
|
|
No quotes option
Previously, SqlAnswersMail put double-quotes around each field in a CSV attachment. A new parameter has been added, @quote_all, which is TRUE by default. By setting this parameter to FALSE, SqlAnswersMail will only put double-quotes around those fields that require to be surrounded by double-quotes by the CSV specification.
|
|
Sending via a specific mail server
Up to now, it was possible to define two mail servers in the SqlAnswersMail Configuration utility. At run-time, SqlAnswersMail tried to send email via the primary mail server and, if it failed, tried to send email via the secondary mail server. It was suggested that it should be possible to define the mail server via a parameter to the sp_sendSAM call.
A new optional parameter, @mail_server, has been added to sp_sendSAM. This parameter is empty by default, so it will not break existing code written around SqlAnswersMail. Prior to using this parameter, it's necessary to set up a Mail Server profile using the SqlAnswersMail Configuration utility. The name of the profile can then be passed in the @mail_server parameter.
|
|
Suppress datetime in a queued email
Previously, when using queuing, each sub-email contained a header with a subject line and a datetime stamp. A new checkbox called Suppress Header has been added to the SqlAnswersMail Configuration, Queuing tab. By switching this textbox to TRUE, you can now suppress headers in queued email.
|
|
|
| |
No existing issues have been resolved in this release
|
|
|
Version:
3.2.0.5
1/21/2007
|
|
|
Download Setup
|
No new features have been added in this release
|
| |
| Resolved Issues |
|
A bug has been identified and resolved in version 3.2.0.5 and later.
|
|
|
|
Version:
3.2.0.4
1/2/2007
|
|
|
Download Setup
|
| New Features | |
Debugging Suport
A feature was added that would allow SqlAnswersMail to track and time all the internal actions.
|
|
|
| |
No existing issues have been resolved in this release
|
|
|
Version:
3.2.0.1
11/22/2006
|
|
|
Download Setup
|
| New Features | |
Clear Queue
Queuing, as it's implemented in SqlAnswersMail, provides the ability to queue and consolidate multiple emails. Queuing is useful when you want to decrease the number of emails sent to your business users.
While queuing was part of SqlAnswersMail since version 3, this release of the software makes it possible to clear an existing queue by using @call_mode = 'clearqueue'. This gives a DBA more control over when and how queues are processed.
|
|
EmailWhenQueryEmpty
It's now possible to control whether empty query resultsets are sent out on a per email basis. When this parameter is set to TRUE (the default), even if the @query parameter did not produce any rows, the email is still sent out to a user. If this parameter is set to FALSE, then emails that have empty resultsets attached are disregarded.
|
|
Images in HTML
When an email is formatted in HTML, it's now possible to use @EMBED() statements to embed images. In the following example, a SampleImage.jpg is used as a background.
<body style="background-image:url(@embed(C:\SampleImage.JPG))"></body>
Please note that all paths must be local to a SQL Server where SqlAnswersMail is installed on.
|
|
Test Emails
This version of the product addresses a common complaint that test emails generated by SqlAnswersMail are not descriptive enough. All test emails now include the name of the server, key configuration information and SqlAnswersMail version information.
|
|
|
| |
| Resolved Issues |
|
It's been reported that if one of the columns in the @query resultset contains only NULLs or blanks, it may lead to the following error.
Error: Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another.
This issue has been corrected.
|
|
The previous version of SqlAnswersMail would always terminate execution upon encountering an exception. While in most cases this is the desired behavior, sometimes it's necessary to continue processing email even if there is an error.
Two common scenarios are using @one_per_recipient parameter or using queuing. In both cases, you may be processing thousands of individual emails, and even if one fails, you want to continue processing others. Setting @ExceptionMode to CONTINUE does exactly that -- it will report and/or log an error but continue execution to the next email.
|
|
|