This is not true. There is 1 and ONLY 1 way to order results from sql server and that is by...

<-- When typing there is a box over on the left. You can click any of those and it will insert the tag into the text box over here where...

Probably because of some oddball characters. You should put it in the code tag

USE [msdb]

GO

XXXXX msdb.dbo.sp_add_alert @name=N’Severity 016',

@message_id=0,

@severity=16,

@enabled=1,

@delay_between_responses=60,

@include_event_description_in=1,

@job_id=N’00000000-0000-0000-0000-000000000000'

GO

XXXXX msdb.dbo.sp_add_notification @alert_name=N’Severity 016', @operator_name=N’SQL Server Administrator’, @notification_method = 7

GO

Results:

1> USE [msdb]

2> GO

Changed...

duplicate post. Please provide all responses here

Certainly making your fields nvarchar will allow for that if it ever happens. It doesn't hurt anything, it just takes twice the storage which is really not a big deal...

Steve Jones - SSC Editor (5/16/2011)

---

I think I use varchar(250) for mine.

Ultimately there is no difference to SQL Server if it's varchar(36) or varchar(1000) other than what the upper limit...

So you are trying to change the name of the parameter that is sent back from a sproc? I can't for the life of me come up with a scenario...

Are you trying to set the presentation value to 'Results'? I don't quite get what you are going for here.

ahh gotcha it is doing int division. Since you original values do not have a decimal place they will be interpreted as an int. You need to force it use...

You certainly don't need to use nvarchar for an email address. Your current 36 is WAY too small. On the other hand you will find some people out there that...

Not sure I understand how dividing by 100 is rounding. All that does is move the decimal place two places to the left.

Here is some code that should let you get what you need.

create table #test

(

HasContract bit,

ExpirationDate date,

ExpirationNotificationDate date

)

insert #test select 1, '12/31/2011', null

update #test set ExpirationNotificationDate = DATEADD(d, -6, DATEADD(m, -1,...

divide by 100?

I am assuming you are not using msdb? Add msdb to your proc call and that should fix it.

Dugi (5/13/2011)

---

Ooops sorry for the same post, I didn't...