GaryCI
Programmer
- May 21, 2008
- 1
- 0
- 0
Details:
Routine is compiled and working called EDWGetChangeDate and should accept value of 'dummy' and return a datetime value. Test works.
A Fact Job declares the following Parameter:
Parameter name: changeCaptureDate
Prompt: Change Date
Type: String
Default value: EDWGetChangeDate('dummy')
ODBC task in the Fact Job has following SQL Code in Outputs/SQL Query tabs
where
(so.DateUpdated > '#changeCaptureDate#'
or s.DateUpdated > '#changeCaptureDate#'
In production the job changes #changeCaptureDate# into a datetime value and SQL works. In development server it changes the value to 'EDWGetChangeDate('dummy')' as if it is a string value, not a routine to run.
I have compiled the Fact job and Routine on the development server. Any idea's why this would NOT see this as a routine to run and instead sees it as a string of text?
Routine is compiled and working called EDWGetChangeDate and should accept value of 'dummy' and return a datetime value. Test works.
A Fact Job declares the following Parameter:
Parameter name: changeCaptureDate
Prompt: Change Date
Type: String
Default value: EDWGetChangeDate('dummy')
ODBC task in the Fact Job has following SQL Code in Outputs/SQL Query tabs
where
(so.DateUpdated > '#changeCaptureDate#'
or s.DateUpdated > '#changeCaptureDate#'
In production the job changes #changeCaptureDate# into a datetime value and SQL works. In development server it changes the value to 'EDWGetChangeDate('dummy')' as if it is a string value, not a routine to run.
I have compiled the Fact job and Routine on the development server. Any idea's why this would NOT see this as a routine to run and instead sees it as a string of text?
