Viewing 15 posts - 16 through 30 (of 36 total)
So my fact table looks like this (excluding date fields)
clientcode valid_from valid_till stock value ValidFromId ValidToID
123 ...
November 18, 2008 at 8:07 am
Hi,
So that means three records, have to be represented as (170+ records) and one record for each day..
1st record in FACT Table ---> -----> 123 ...
November 15, 2008 at 10:54 pm
Finally narrowed down the issue. The cause is PGP encryption. When the BAT file which encrypts or decrypts data fails. It corrupts Agents Command Shell.
How to prevent it ?
Deepak
October 7, 2008 at 7:42 am
Its for the support team , they have to keep an eye on failed/running jobs and they like EM
Deepak
November 14, 2007 at 7:39 am
Hi Rudy,
We are capturing the output, unfortunately the log file is empty and the time stamp of the file is not changing, which makes be beleive that BAT file is...
August 2, 2007 at 9:18 am
It happened again today... will applying SP4 will help...
Deepak
August 2, 2007 at 8:15 am
Hi,
When we run the batch file from command prompt it works fine with the same account with which agent is running with. But not from agent. When we restarted agent...
June 22, 2007 at 6:23 am
When I restarted the AGENT all jobs ran fine. So its clear that permission is not the issue.
CMDEXEC step from all the jobs which were executing BAT file run successfully ...
June 20, 2007 at 7:34 am
Hi,
I found out that couple of other jobs which had BAT file also behaved in same manner.
Is it somthing to do with env. or SQL Agent. Will it make a...
June 19, 2007 at 5:42 am
Hi,
Both the log files are empty (Step log and batch file log  , thats the issue. no place to see what exactly happened.
Step history shows
Executed...
June 19, 2007 at 4:17 am
hi,
use data converstion transformation between source and target. Since the source is CHAR there could be a chance that invalid data exists i.e. source is having char other than 0 or 1.
Deepak
June 2, 2007 at 2:07 am
Please ignore it ... Got the solution
February 16, 2007 at 9:28 am
Thanks Carl, It was index with bit field plus Parallel Query causing the issue. As mentioned in the KB article http://support.microsoft.com/kb/824018/
For the time being I have changed...
February 15, 2007 at 4:23 am
SAGA Continues...
What I observered in last two weeks, when ever I run DEFRAG , logshipping goes out of sync..
Nextx week will run TRACE on log_SHIPPING* tables to see what exactally...
October 20, 2006 at 1:20 am
Viewing 15 posts - 16 through 30 (of 36 total)