Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
SQL
ce
clients
clustering
connect
datamining
datawarehouse
dts
fulltext
jdbcdriver
msde
mseq
newusers
notificationsvcs
odbc
olap
programming
replication
reportingsvcs
security
securitytools
server
setup
sqlxml.viewmapper
tools
xml
  
 
date: Thu, 8 Mar 2007 01:38:13 -0800,    group: microsoft.public.sqlserver.notificationsvcs        back       


NSSetQuantumClockDate question   
Hi,
I'm working through the Stock sample walkthrough in the SQL Server 2000 
Notification Services SP1 help file (our client has SQL Server 2000 so this 
is required).

I have a question relating to the value that is passed to the 
NSSetQuantumClockDate stored procedure.

Firstly, I should point out that the server default and login languages are 
set to British English.

I am at Task 5: Adding a Notification Generation Rule if you want to refer 
to the walkthrough text.

When I follow the instructions, I use the following call:

   EXEC NSSetQuantumClockDate '2007-03-07 10:41:34.960'

The UTC date was copied from the output from a call to NSEventBatchDetails. 
The date is 7th March 2007.

However, when I call 
   EXEC NSPrepareRuleFiring 0, 0 
I get error '4016: The quantum end time is later than the current real clock 
time.  Notification Services cannot process events that occur in the future.'

Upon further investigation the input date to NSSetQuantumClockDate was 
interpreted as 3rd July 2007.

To overcome this error I changed the input to NSSetQuantumClockDate to 
'2007-07-03 10:41:34.960'.

I'd like to understand why the original input to NSSetQuantumClockDate was 
not processed as I had expected.

Is there some configuration I need to apply to ensure the date is processed 
as 'yyyy-mm-dd ...' ?

-- 
Regards,
Craig
date: Thu, 8 Mar 2007 01:38:13 -0800   author:   Craig am

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us