problem with sql mail

i have configured sql mail to send emails to outlook with exchange server
running with outlook ... but the problem iam facing is that although the
option of "sent messages to the sent items folder " is cliecked under the
sql agent mail and also in the outlook but still any mail that goes through
sql mail is delivered successfully to the recipient but does not go the sent
items folder of outlook
would appreciate any help on this thnaksIf you are running SQL Server 2000, SQL Mail for SQL Server
2000 does not save a copy of sent messages in the Sent Items
folder. If you need a copy of the messages, you need to cc:
them to an exchange account and create an Outlook message
rule that routes these message copies to the Sent Items
folder.
For more info, refer to:
INF: Common SQL Mail Problems
http://support.microsoft.com/?scid=315886
The section: Q7: Why do I not have any sent messages in the
Sent Items folder explains this issue.
-Sue
On Sun, 7 Mar 2004 15:09:13 +1100, "afsheen"
<afsheenj@.hotmial.com> wrote:

>i have configured sql mail to send emails to outlook with exchange server
>running with outlook ... but the problem iam facing is that although the
>option of "sent messages to the sent items folder " is cliecked under the
>sql agent mail and also in the outlook but still any mail that goes through
>sql mail is delivered successfully to the recipient but does not go the sen
t
>items folder of outlook
>would appreciate any help on this thnaks
>

Problem with parenthesis in the default value of a column

I am having a problem with the format of default values in SQL Server 2005.
I
am using a legacy application that is not expecting the double parenthesis
around the default value that SQL Server adds. For instance, if
I set 0 (zero) as the default value for a column of type int as follows
ALTER TABLE Entity ADD CONSTRAINT [DF_Entity_Class] DEFAULT 0 FOR
Class)
then SQL Server will set the default value as ((0)). The problem is that the
legacy application is validating the default values and expecting just 0. I
own the database but have no control over the application. Therefore, I
cannot change the application to remove the parenthesis after reading the
value.
Is there any way to force SQL Server to store the default value without the
parenthesis or to return it without the parenthesis (note that the
application is reading the database tables directly).
Regards,
ArturHi
I don't think you can change the way it is stored but you could use the
REPLACE function to strip out the braces when you return it.
John
"artur" wrote:

> I am having a problem with the format of default values in SQL Server 2005
. I
> am using a legacy application that is not expecting the double parenthesis
> around the default value that SQL Server adds. For instance, if
> I set 0 (zero) as the default value for a column of type int as follows
> ALTER TABLE Entity ADD CONSTRAINT [DF_Entity_Class] DEFAULT 0 FOR
> Class)
> then SQL Server will set the default value as ((0)). The problem is that t
he
> legacy application is validating the default values and expecting just 0.
I
> own the database but have no control over the application. Therefore, I
> cannot change the application to remove the parenthesis after reading the
> value.
> Is there any way to force SQL Server to store the default value without th
e
> parenthesis or to return it without the parenthesis (note that the
> application is reading the database tables directly).
> Regards,
> Artur