Dear all,
I have scheduled some jobs in SQL Server Agent to run some DTS packages. The
original owner of these jobs is "sa". However, when I changed to the owner to
be another SQL login id, e.g. myUser, the scheduled jobs failed. "myUser" has
the "db_owner" role. The owner of DTS packages is "Domain\Administrator" and
I logon the Windows server as local Administrator. I am not sure if there is
any problem on this. Can anyone advise? Thanks.
Ivan
If the job is owned by sa or a login that is a member of the
sysadmins server role, then the job executes under the
security context of the SQL Server Agent service account. If
the job is owned by a login that is not a member of the
sysadmins server role, then the job is executed under the
security context of the proxy account.
And then...the default setting for SQL Agent is that
non-sysadmins cannot execute CmdExec or ActiveX scripting
jobs. Scheduling a package is done by executing a CmdExec
step in the job.
That the basics of it and why you are having problems with
your job. You can find more information in the following
article:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On Mon, 31 Oct 2005 20:34:02 -0800, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
>Dear all,
>I have scheduled some jobs in SQL Server Agent to run some DTS packages. The
>original owner of these jobs is "sa". However, when I changed to the owner to
>be another SQL login id, e.g. myUser, the scheduled jobs failed. "myUser" has
>the "db_owner" role. The owner of DTS packages is "Domain\Administrator" and
>I logon the Windows server as local Administrator. I am not sure if there is
>any problem on this. Can anyone advise? Thanks.
>Ivan
sql
Showing posts with label dear. Show all posts
Showing posts with label dear. Show all posts
Friday, March 23, 2012
Job ownership problem
Dear all,
I have scheduled some jobs in SQL Server Agent to run some DTS packages. The
original owner of these jobs is "sa". However, when I changed to the owner t
o
be another SQL login id, e.g. myUser, the scheduled jobs failed. "myUser" ha
s
the "db_owner" role. The owner of DTS packages is "Domain\Administrator" and
I logon the Windows server as local Administrator. I am not sure if there is
any problem on this. Can anyone advise? Thanks.
IvanIf the job is owned by sa or a login that is a member of the
sysadmins server role, then the job executes under the
security context of the SQL Server Agent service account. If
the job is owned by a login that is not a member of the
sysadmins server role, then the job is executed under the
security context of the proxy account.
And then...the default setting for SQL Agent is that
non-sysadmins cannot execute CmdExec or ActiveX scripting
jobs. Scheduling a package is done by executing a CmdExec
step in the job.
That the basics of it and why you are having problems with
your job. You can find more information in the following
article:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On Mon, 31 Oct 2005 20:34:02 -0800, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
>Dear all,
>I have scheduled some jobs in SQL Server Agent to run some DTS packages. Th
e
>original owner of these jobs is "sa". However, when I changed to the owner
to
>be another SQL login id, e.g. myUser, the scheduled jobs failed. "myUser" h
as
>the "db_owner" role. The owner of DTS packages is "Domain\Administrator" an
d
>I logon the Windows server as local Administrator. I am not sure if there i
s
>any problem on this. Can anyone advise? Thanks.
>Ivan
I have scheduled some jobs in SQL Server Agent to run some DTS packages. The
original owner of these jobs is "sa". However, when I changed to the owner t
o
be another SQL login id, e.g. myUser, the scheduled jobs failed. "myUser" ha
s
the "db_owner" role. The owner of DTS packages is "Domain\Administrator" and
I logon the Windows server as local Administrator. I am not sure if there is
any problem on this. Can anyone advise? Thanks.
IvanIf the job is owned by sa or a login that is a member of the
sysadmins server role, then the job executes under the
security context of the SQL Server Agent service account. If
the job is owned by a login that is not a member of the
sysadmins server role, then the job is executed under the
security context of the proxy account.
And then...the default setting for SQL Agent is that
non-sysadmins cannot execute CmdExec or ActiveX scripting
jobs. Scheduling a package is done by executing a CmdExec
step in the job.
That the basics of it and why you are having problems with
your job. You can find more information in the following
article:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On Mon, 31 Oct 2005 20:34:02 -0800, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
>Dear all,
>I have scheduled some jobs in SQL Server Agent to run some DTS packages. Th
e
>original owner of these jobs is "sa". However, when I changed to the owner
to
>be another SQL login id, e.g. myUser, the scheduled jobs failed. "myUser" h
as
>the "db_owner" role. The owner of DTS packages is "Domain\Administrator" an
d
>I logon the Windows server as local Administrator. I am not sure if there i
s
>any problem on this. Can anyone advise? Thanks.
>Ivan
Wednesday, March 21, 2012
Job ownership problem
Dear all,
I have scheduled some jobs in SQL Server Agent to run some DTS packages. The
original owner of these jobs is "sa". However, when I changed to the owner to
be another SQL login id, e.g. myUser, the scheduled jobs failed. "myUser" has
the "db_owner" role. The owner of DTS packages is "Domain\Administrator" and
I logon the Windows server as local Administrator. I am not sure if there is
any problem on this. Can anyone advise? Thanks.
IvanIf the job is owned by sa or a login that is a member of the
sysadmins server role, then the job executes under the
security context of the SQL Server Agent service account. If
the job is owned by a login that is not a member of the
sysadmins server role, then the job is executed under the
security context of the proxy account.
And then...the default setting for SQL Agent is that
non-sysadmins cannot execute CmdExec or ActiveX scripting
jobs. Scheduling a package is done by executing a CmdExec
step in the job.
That the basics of it and why you are having problems with
your job. You can find more information in the following
article:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On Mon, 31 Oct 2005 20:34:02 -0800, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
>Dear all,
>I have scheduled some jobs in SQL Server Agent to run some DTS packages. The
>original owner of these jobs is "sa". However, when I changed to the owner to
>be another SQL login id, e.g. myUser, the scheduled jobs failed. "myUser" has
>the "db_owner" role. The owner of DTS packages is "Domain\Administrator" and
>I logon the Windows server as local Administrator. I am not sure if there is
>any problem on this. Can anyone advise? Thanks.
>Ivan
I have scheduled some jobs in SQL Server Agent to run some DTS packages. The
original owner of these jobs is "sa". However, when I changed to the owner to
be another SQL login id, e.g. myUser, the scheduled jobs failed. "myUser" has
the "db_owner" role. The owner of DTS packages is "Domain\Administrator" and
I logon the Windows server as local Administrator. I am not sure if there is
any problem on this. Can anyone advise? Thanks.
IvanIf the job is owned by sa or a login that is a member of the
sysadmins server role, then the job executes under the
security context of the SQL Server Agent service account. If
the job is owned by a login that is not a member of the
sysadmins server role, then the job is executed under the
security context of the proxy account.
And then...the default setting for SQL Agent is that
non-sysadmins cannot execute CmdExec or ActiveX scripting
jobs. Scheduling a package is done by executing a CmdExec
step in the job.
That the basics of it and why you are having problems with
your job. You can find more information in the following
article:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On Mon, 31 Oct 2005 20:34:02 -0800, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
>Dear all,
>I have scheduled some jobs in SQL Server Agent to run some DTS packages. The
>original owner of these jobs is "sa". However, when I changed to the owner to
>be another SQL login id, e.g. myUser, the scheduled jobs failed. "myUser" has
>the "db_owner" role. The owner of DTS packages is "Domain\Administrator" and
>I logon the Windows server as local Administrator. I am not sure if there is
>any problem on this. Can anyone advise? Thanks.
>Ivan
job keep running if fail
Dear All
In SQL Server 2000, I schedule a job to run a exe. I expect the return of this result show the success or fail. However, I find the job keep running if fail. Actually, I want to see the failed status in enterprise manager.
Could you give me some suggestions how to return a fail from VB6 program to SQL Server? Maybe give me other directions to solve the problem? Thanks a lot.
More Information
I run the exe by double click. if it fail, it return a prompt message box.
Alex
This is a SSIS not DTS or VB6 forum, so you may get better responses on a more appropriate forum or newsgroup-
http://www.devx.com/vb2themax/Tip/18288
|||Reading again is see you mention a message box. This will cause the scheduled job to just hang. You should never throw message boxes or any other form of UI when running unattended. I think there may have been an option suppress errors in message boxes, somewhere in project properties, but it has been a long time since I used VB6. Try the newsgroup, or just searching Google Groups.
sqlJob issue
Dear all,
I want to define a job which might be able to launch a .BAT where its
location is my local workstation. Is it possible? That .BAT call a .EXE and
we wish to keep out of our production server. That job will be scheduled fro
m
the server...
Thanks a lot,There are a couple of things to consider here. If you create the job on your
sql server, and have the first step be an OS Command (CmdExec) with a value
like
\\yourworkstation\c$\yourbatch.bat
-although the file resides on the machine yourworkstation, the program is
actually executed from the server (and since the exe that the bat file calls
won't be on the server, it will fail)
-if the sql server is running under the local system account, you won't be
able to connect over the network to your workstation anyway.
If you needed the program to physically reside and execute from your
workstation, you're best bet would be to create a scheduled task on your
workstation, and call the command from the sql server like
schtasks /run /tn YourTask /s yourworkstation
where YourTask is the name given to your task when you create it. If the sql
server is running under the local system account, you will need to specify a
user account that has local administrative priveledges on yourworkstation,
like so
schtasks /run /tn YourTask /s yourworkstation /u administrator /p password
The security implications here are that you have an administrator password
stored with the job on the sql server.
"Enric" wrote:
> Dear all,
> I want to define a job which might be able to launch a .BAT where its
> location is my local workstation. Is it possible? That .BAT call a .EXE an
d
> we wish to keep out of our production server. That job will be scheduled f
rom
> the server...
> Thanks a lot,
I want to define a job which might be able to launch a .BAT where its
location is my local workstation. Is it possible? That .BAT call a .EXE and
we wish to keep out of our production server. That job will be scheduled fro
m
the server...
Thanks a lot,There are a couple of things to consider here. If you create the job on your
sql server, and have the first step be an OS Command (CmdExec) with a value
like
\\yourworkstation\c$\yourbatch.bat
-although the file resides on the machine yourworkstation, the program is
actually executed from the server (and since the exe that the bat file calls
won't be on the server, it will fail)
-if the sql server is running under the local system account, you won't be
able to connect over the network to your workstation anyway.
If you needed the program to physically reside and execute from your
workstation, you're best bet would be to create a scheduled task on your
workstation, and call the command from the sql server like
schtasks /run /tn YourTask /s yourworkstation
where YourTask is the name given to your task when you create it. If the sql
server is running under the local system account, you will need to specify a
user account that has local administrative priveledges on yourworkstation,
like so
schtasks /run /tn YourTask /s yourworkstation /u administrator /p password
The security implications here are that you have an administrator password
stored with the job on the sql server.
"Enric" wrote:
> Dear all,
> I want to define a job which might be able to launch a .BAT where its
> location is my local workstation. Is it possible? That .BAT call a .EXE an
d
> we wish to keep out of our production server. That job will be scheduled f
rom
> the server...
> Thanks a lot,
Monday, March 12, 2012
Job Failure
Dear All
A quick question:
I run a set of scheduled jobs. The jobs run Stored Procedures.
However, if the sproc fails, the job quits and moves on to the next
one. However, the sproc should carry on. E.g, IF find bad records,
EXPORT to file, GO TO NEXT RECORD (BUT DON'T QUIT THE SPROC). The job
scheduler does not allow this, therefore, the sproc does not get a
chance to finish.
Is there a way to ensure a sproc can finish before moving on to the
next step?
Thanks
Simonaaronss@.the-mdu.com (Simon) wrote in message news:<f526ea06.0402050300.499b8b81@.posting.google.com>...
> Dear All
> A quick question:
> I run a set of scheduled jobs. The jobs run Stored Procedures.
> However, if the sproc fails, the job quits and moves on to the next
> one. However, the sproc should carry on. E.g, IF find bad records,
> EXPORT to file, GO TO NEXT RECORD (BUT DON'T QUIT THE SPROC). The job
> scheduler does not allow this, therefore, the sproc does not get a
> chance to finish.
> Is there a way to ensure a sproc can finish before moving on to the
> next step?
> Thanks
> Simon
I'm not sure I understand you exactly - I guess the issue is not
really the scheduling, but rather how to handle an error in your
stored procedure? If the procedure exists because of an error, then
control goes back to the scheduled job. You could set a number of
retry attempts for that job step, but it would probably be better to
handle or prevent the error in your procedure. There are some useful
articles here:
http://www.sommarskog.se/index.html
If this isn't helpful, perhaps you could post (some of) your procedure
code to show where it fails, along with the error message, and someone
may be able to suggest how to handle the error condition.
Simon
Friday, March 9, 2012
Job Execution sometimes failed
Dear All,
I have a problem with sql server jobs.
The jobs are executing DTS Package in scheculed manner.
The problem is the sometimes the schedule failed, and i don't know what
made the jobs failed.
And I have tried to trace it, but still coundn't find the problem.
Does anyone can help me out?
Thanks
Robert LieTry switching on Package logging in your DTS Packages. Right click in the
DTS Package, choose Package Properties and then Logging. When the job fails
again, you can then check the Package log (right-click the DTS Package in
Enterprise Manager, then choose package logs...). Hopefully you will find
the answer in there.
--
Jacco Schalkwijk
SQL Server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%2397xWRfuFHA.2540@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I have a problem with sql server jobs.
> The jobs are executing DTS Package in scheculed manner.
> The problem is the sometimes the schedule failed, and i don't know what
> made the jobs failed.
> And I have tried to trace it, but still coundn't find the problem.
> Does anyone can help me out?
> Thanks
> Robert Lie|||This is the error message when the job failed:
Executed as user: <domain>/<user>. ...un OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTS... Process
Exit Code -1073741819. The step failed.
Thanks
Robert Lie
Jacco Schalkwijk wrote:
> Try switching on Package logging in your DTS Packages. Right click in the
> DTS Package, choose Package Properties and then Logging. When the job fails
> again, you can then check the Package log (right-click the DTS Package in
> Enterprise Manager, then choose package logs...). Hopefully you will find
> the answer in there.
>|||For the pump, you can set it to allow a certain number of errors, then log
these errors to a file, this should help you find what the pump is failing
on
If it is a Transform Data Task...Select The Properties..Then the Options
Tab...Enter an Exception File....Set Max Error Count to SOmething Like
9999...Run The Step...Review The Exception Log
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...
> This is the error message when the job failed:
> Executed as user: <domain>/<user>. ...un OnStart:
> DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_6
> DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTS... Process Exit Code -1073741819. The step
> failed.
>
> Thanks
> Robert Lie
> Jacco Schalkwijk wrote:
>> Try switching on Package logging in your DTS Packages. Right click in the
>> DTS Package, choose Package Properties and then Logging. When the job
>> fails again, you can then check the Package log (right-click the DTS
>> Package in Enterprise Manager, then choose package logs...). Hopefully
>> you will find the answer in there.|||Ok. I'll try your idea anyway.
I want to tell you how the DTS Package works:
1. Disable ALL contraint from all tables in a database
2. If success then continue to delete all the tables
3. Fill the deleted tables from another tables from another server
4. Update some values in certain tables
Maybe you see something wrong in that work flow?
Thanks
Robert Lie
David J. Cartwright wrote:
> For the pump, you can set it to allow a certain number of errors, then log
> these errors to a file, this should help you find what the pump is failing
> on
> If it is a Transform Data Task...Select The Properties..Then the Options
> Tab...Enter an Exception File....Set Max Error Count to SOmething Like
> 9999...Run The Step...Review The Exception Log
> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
> news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...
>>This is the error message when the job failed:
>>Executed as user: <domain>/<user>. ...un OnStart:
>>DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_6
>>DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
>>DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart: DTSStep_DTSDataPumpTask_1
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
>>DTSRun OnStart: DTSStep_DTS... Process Exit Code -1073741819. The step
>>failed.
>>
>>Thanks
>>Robert Lie
>>Jacco Schalkwijk wrote:
>>Try switching on Package logging in your DTS Packages. Right click in the
>>DTS Package, choose Package Properties and then Logging. When the job
>>fails again, you can then check the Package log (right-click the DTS
>>Package in Enterprise Manager, then choose package logs...). Hopefully
>>you will find the answer in there.
>
>|||do you actualy delete/recreate the table, or do you use TRUNCATE, and also,
why dont you do the updates in the DTS Transformation, maybe then you can
keep contrainsts
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:ei%23VHiguFHA.2620@.TK2MSFTNGP10.phx.gbl...
> Ok. I'll try your idea anyway.
> I want to tell you how the DTS Package works:
> 1. Disable ALL contraint from all tables in a database
> 2. If success then continue to delete all the tables
> 3. Fill the deleted tables from another tables from another server
> 4. Update some values in certain tables
> Maybe you see something wrong in that work flow?
> Thanks
> Robert Lie
>
> David J. Cartwright wrote:
>> For the pump, you can set it to allow a certain number of errors, then
>> log these errors to a file, this should help you find what the pump is
>> failing on
>> If it is a Transform Data Task...Select The Properties..Then the Options
>> Tab...Enter an Exception File....Set Max Error Count to SOmething Like
>> 9999...Run The Step...Review The Exception Log
>> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
>> news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...
>>This is the error message when the job failed:
>>Executed as user: <domain>/<user>. ...un OnStart:
>>DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
>>DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10
>>DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTS... Process Exit
>>Code -1073741819. The step failed.
>>
>>Thanks
>>Robert Lie
>>Jacco Schalkwijk wrote:
>>Try switching on Package logging in your DTS Packages. Right click in
>>the DTS Package, choose Package Properties and then Logging. When the
>>job fails again, you can then check the Package log (right-click the DTS
>>Package in Enterprise Manager, then choose package logs...). Hopefully
>>you will find the answer in there.
>>
I have a problem with sql server jobs.
The jobs are executing DTS Package in scheculed manner.
The problem is the sometimes the schedule failed, and i don't know what
made the jobs failed.
And I have tried to trace it, but still coundn't find the problem.
Does anyone can help me out?
Thanks
Robert LieTry switching on Package logging in your DTS Packages. Right click in the
DTS Package, choose Package Properties and then Logging. When the job fails
again, you can then check the Package log (right-click the DTS Package in
Enterprise Manager, then choose package logs...). Hopefully you will find
the answer in there.
--
Jacco Schalkwijk
SQL Server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%2397xWRfuFHA.2540@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I have a problem with sql server jobs.
> The jobs are executing DTS Package in scheculed manner.
> The problem is the sometimes the schedule failed, and i don't know what
> made the jobs failed.
> And I have tried to trace it, but still coundn't find the problem.
> Does anyone can help me out?
> Thanks
> Robert Lie|||This is the error message when the job failed:
Executed as user: <domain>/<user>. ...un OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTS... Process
Exit Code -1073741819. The step failed.
Thanks
Robert Lie
Jacco Schalkwijk wrote:
> Try switching on Package logging in your DTS Packages. Right click in the
> DTS Package, choose Package Properties and then Logging. When the job fails
> again, you can then check the Package log (right-click the DTS Package in
> Enterprise Manager, then choose package logs...). Hopefully you will find
> the answer in there.
>|||For the pump, you can set it to allow a certain number of errors, then log
these errors to a file, this should help you find what the pump is failing
on
If it is a Transform Data Task...Select The Properties..Then the Options
Tab...Enter an Exception File....Set Max Error Count to SOmething Like
9999...Run The Step...Review The Exception Log
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...
> This is the error message when the job failed:
> Executed as user: <domain>/<user>. ...un OnStart:
> DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_6
> DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTS... Process Exit Code -1073741819. The step
> failed.
>
> Thanks
> Robert Lie
> Jacco Schalkwijk wrote:
>> Try switching on Package logging in your DTS Packages. Right click in the
>> DTS Package, choose Package Properties and then Logging. When the job
>> fails again, you can then check the Package log (right-click the DTS
>> Package in Enterprise Manager, then choose package logs...). Hopefully
>> you will find the answer in there.|||Ok. I'll try your idea anyway.
I want to tell you how the DTS Package works:
1. Disable ALL contraint from all tables in a database
2. If success then continue to delete all the tables
3. Fill the deleted tables from another tables from another server
4. Update some values in certain tables
Maybe you see something wrong in that work flow?
Thanks
Robert Lie
David J. Cartwright wrote:
> For the pump, you can set it to allow a certain number of errors, then log
> these errors to a file, this should help you find what the pump is failing
> on
> If it is a Transform Data Task...Select The Properties..Then the Options
> Tab...Enter an Exception File....Set Max Error Count to SOmething Like
> 9999...Run The Step...Review The Exception Log
> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
> news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...
>>This is the error message when the job failed:
>>Executed as user: <domain>/<user>. ...un OnStart:
>>DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_6
>>DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
>>DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart: DTSStep_DTSDataPumpTask_1
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
>>DTSRun OnStart: DTSStep_DTS... Process Exit Code -1073741819. The step
>>failed.
>>
>>Thanks
>>Robert Lie
>>Jacco Schalkwijk wrote:
>>Try switching on Package logging in your DTS Packages. Right click in the
>>DTS Package, choose Package Properties and then Logging. When the job
>>fails again, you can then check the Package log (right-click the DTS
>>Package in Enterprise Manager, then choose package logs...). Hopefully
>>you will find the answer in there.
>
>|||do you actualy delete/recreate the table, or do you use TRUNCATE, and also,
why dont you do the updates in the DTS Transformation, maybe then you can
keep contrainsts
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:ei%23VHiguFHA.2620@.TK2MSFTNGP10.phx.gbl...
> Ok. I'll try your idea anyway.
> I want to tell you how the DTS Package works:
> 1. Disable ALL contraint from all tables in a database
> 2. If success then continue to delete all the tables
> 3. Fill the deleted tables from another tables from another server
> 4. Update some values in certain tables
> Maybe you see something wrong in that work flow?
> Thanks
> Robert Lie
>
> David J. Cartwright wrote:
>> For the pump, you can set it to allow a certain number of errors, then
>> log these errors to a file, this should help you find what the pump is
>> failing on
>> If it is a Transform Data Task...Select The Properties..Then the Options
>> Tab...Enter an Exception File....Set Max Error Count to SOmething Like
>> 9999...Run The Step...Review The Exception Log
>> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
>> news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...
>>This is the error message when the job failed:
>>Executed as user: <domain>/<user>. ...un OnStart:
>>DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
>>DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10
>>DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
>>DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
>>DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTS... Process Exit
>>Code -1073741819. The step failed.
>>
>>Thanks
>>Robert Lie
>>Jacco Schalkwijk wrote:
>>Try switching on Package logging in your DTS Packages. Right click in
>>the DTS Package, choose Package Properties and then Logging. When the
>>job fails again, you can then check the Package log (right-click the DTS
>>Package in Enterprise Manager, then choose package logs...). Hopefully
>>you will find the answer in there.
>>
Job Execution sometimes failed
Dear All,
I have a problem with sql server jobs.
The jobs are executing DTS Package in scheculed manner.
The problem is the sometimes the schedule failed, and i don't know what
made the jobs failed.
And I have tried to trace it, but still coundn't find the problem.
Does anyone can help me out?
Thanks
Robert LieTry switching on Package logging in your DTS Packages. Right click in the
DTS Package, choose Package Properties and then Logging. When the job fails
again, you can then check the Package log (right-click the DTS Package in
Enterprise Manager, then choose package logs...). Hopefully you will find
the answer in there.
Jacco Schalkwijk
SQL Server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%2397xWRfuFHA.2540@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I have a problem with sql server jobs.
> The jobs are executing DTS Package in scheculed manner.
> The problem is the sometimes the schedule failed, and i don't know what
> made the jobs failed.
> And I have tried to trace it, but still coundn't find the problem.
> Does anyone can help me out?
> Thanks
> Robert Lie|||This is the error message when the job failed:
Executed as user: <domain>/<user>. ...un OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTS... Process
Exit Code -1073741819. The step failed.
Thanks
Robert Lie
Jacco Schalkwijk wrote:
> Try switching on Package logging in your DTS Packages. Right click in the
> DTS Package, choose Package Properties and then Logging. When the job fail
s
> again, you can then check the Package log (right-click the DTS Package in
> Enterprise Manager, then choose package logs...). Hopefully you will find
> the answer in there.
>|||For the pump, you can set it to allow a certain number of errors, then log
these errors to a file, this should help you find what the pump is failing
on
If it is a Transform Data Task...Select The Properties..Then the Options
Tab...Enter an Exception File....Set Max Error Count to SOmething Like
9999...Run The Step...Review The Exception Log
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> This is the error message when the job failed:
> Executed as user: <domain>/<user>. ...un OnStart:
> DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_6
> DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTS... Process Exit Code -1073741819. The step
> failed.
>
> Thanks
> Robert Lie
> Jacco Schalkwijk wrote:|||Ok. I'll try your idea anyway.
I want to tell you how the DTS Package works:
1. Disable ALL contraint from all tables in a database
2. If success then continue to delete all the tables
3. Fill the deleted tables from another tables from another server
4. Update some values in certain tables
Maybe you see something wrong in that work flow?
Thanks
Robert Lie
David J. Cartwright wrote:
> For the pump, you can set it to allow a certain number of errors, then log
> these errors to a file, this should help you find what the pump is failing
> on
> If it is a Transform Data Task...Select The Properties..Then the Options
> Tab...Enter an Exception File....Set Max Error Count to SOmething Like
> 9999...Run The Step...Review The Exception Log
> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
> news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...
>
>
>|||do you actualy delete/recreate the table, or do you use TRUNCATE, and also,
why dont you do the updates in the DTS Transformation, maybe then you can
keep contrainsts
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:ei%23VHiguFHA.2620@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Ok. I'll try your idea anyway.
> I want to tell you how the DTS Package works:
> 1. Disable ALL contraint from all tables in a database
> 2. If success then continue to delete all the tables
> 3. Fill the deleted tables from another tables from another server
> 4. Update some values in certain tables
> Maybe you see something wrong in that work flow?
> Thanks
> Robert Lie
>
> David J. Cartwright wrote:
I have a problem with sql server jobs.
The jobs are executing DTS Package in scheculed manner.
The problem is the sometimes the schedule failed, and i don't know what
made the jobs failed.
And I have tried to trace it, but still coundn't find the problem.
Does anyone can help me out?
Thanks
Robert LieTry switching on Package logging in your DTS Packages. Right click in the
DTS Package, choose Package Properties and then Logging. When the job fails
again, you can then check the Package log (right-click the DTS Package in
Enterprise Manager, then choose package logs...). Hopefully you will find
the answer in there.
Jacco Schalkwijk
SQL Server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%2397xWRfuFHA.2540@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I have a problem with sql server jobs.
> The jobs are executing DTS Package in scheculed manner.
> The problem is the sometimes the schedule failed, and i don't know what
> made the jobs failed.
> And I have tried to trace it, but still coundn't find the problem.
> Does anyone can help me out?
> Thanks
> Robert Lie|||This is the error message when the job failed:
Executed as user: <domain>/<user>. ...un OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTS... Process
Exit Code -1073741819. The step failed.
Thanks
Robert Lie
Jacco Schalkwijk wrote:
> Try switching on Package logging in your DTS Packages. Right click in the
> DTS Package, choose Package Properties and then Logging. When the job fail
s
> again, you can then check the Package log (right-click the DTS Package in
> Enterprise Manager, then choose package logs...). Hopefully you will find
> the answer in there.
>|||For the pump, you can set it to allow a certain number of errors, then log
these errors to a file, this should help you find what the pump is failing
on
If it is a Transform Data Task...Select The Properties..Then the Options
Tab...Enter an Exception File....Set Max Error Count to SOmething Like
9999...Run The Step...Review The Exception Log
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> This is the error message when the job failed:
> Executed as user: <domain>/<user>. ...un OnStart:
> DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_6
> DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTS... Process Exit Code -1073741819. The step
> failed.
>
> Thanks
> Robert Lie
> Jacco Schalkwijk wrote:|||Ok. I'll try your idea anyway.
I want to tell you how the DTS Package works:
1. Disable ALL contraint from all tables in a database
2. If success then continue to delete all the tables
3. Fill the deleted tables from another tables from another server
4. Update some values in certain tables
Maybe you see something wrong in that work flow?
Thanks
Robert Lie
David J. Cartwright wrote:
> For the pump, you can set it to allow a certain number of errors, then log
> these errors to a file, this should help you find what the pump is failing
> on
> If it is a Transform Data Task...Select The Properties..Then the Options
> Tab...Enter an Exception File....Set Max Error Count to SOmething Like
> 9999...Run The Step...Review The Exception Log
> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
> news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...
>
>
>|||do you actualy delete/recreate the table, or do you use TRUNCATE, and also,
why dont you do the updates in the DTS Transformation, maybe then you can
keep contrainsts
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:ei%23VHiguFHA.2620@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Ok. I'll try your idea anyway.
> I want to tell you how the DTS Package works:
> 1. Disable ALL contraint from all tables in a database
> 2. If success then continue to delete all the tables
> 3. Fill the deleted tables from another tables from another server
> 4. Update some values in certain tables
> Maybe you see something wrong in that work flow?
> Thanks
> Robert Lie
>
> David J. Cartwright wrote:
Job Execution sometimes failed
Dear All,
I have a problem with sql server jobs.
The jobs are executing DTS Package in scheculed manner.
The problem is the sometimes the schedule failed, and i don't know what
made the jobs failed.
And I have tried to trace it, but still coundn't find the problem.
Does anyone can help me out?
Thanks
Robert Lie
Try switching on Package logging in your DTS Packages. Right click in the
DTS Package, choose Package Properties and then Logging. When the job fails
again, you can then check the Package log (right-click the DTS Package in
Enterprise Manager, then choose package logs...). Hopefully you will find
the answer in there.
Jacco Schalkwijk
SQL Server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%2397xWRfuFHA.2540@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I have a problem with sql server jobs.
> The jobs are executing DTS Package in scheculed manner.
> The problem is the sometimes the schedule failed, and i don't know what
> made the jobs failed.
> And I have tried to trace it, but still coundn't find the problem.
> Does anyone can help me out?
> Thanks
> Robert Lie
|||This is the error message when the job failed:
Executed as user: <domain>/<user>. ...un OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTS... Process
Exit Code -1073741819. The step failed.
Thanks
Robert Lie
Jacco Schalkwijk wrote:
> Try switching on Package logging in your DTS Packages. Right click in the
> DTS Package, choose Package Properties and then Logging. When the job fails
> again, you can then check the Package log (right-click the DTS Package in
> Enterprise Manager, then choose package logs...). Hopefully you will find
> the answer in there.
>
|||For the pump, you can set it to allow a certain number of errors, then log
these errors to a file, this should help you find what the pump is failing
on
If it is a Transform Data Task...Select The Properties..Then the Options
Tab...Enter an Exception File....Set Max Error Count to SOmething Like
9999...Run The Step...Review The Exception Log
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> This is the error message when the job failed:
> Executed as user: <domain>/<user>. ...un OnStart:
> DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_6
> DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTS... Process Exit Code -1073741819. The step
> failed.
>
> Thanks
> Robert Lie
> Jacco Schalkwijk wrote:
|||Ok. I'll try your idea anyway.
I want to tell you how the DTS Package works:
1. Disable ALL contraint from all tables in a database
2. If success then continue to delete all the tables
3. Fill the deleted tables from another tables from another server
4. Update some values in certain tables
Maybe you see something wrong in that work flow?
Thanks
Robert Lie
David J. Cartwright wrote:
> For the pump, you can set it to allow a certain number of errors, then log
> these errors to a file, this should help you find what the pump is failing
> on
> If it is a Transform Data Task...Select The Properties..Then the Options
> Tab...Enter an Exception File....Set Max Error Count to SOmething Like
> 9999...Run The Step...Review The Exception Log
> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
> news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...
>
>
|||do you actualy delete/recreate the table, or do you use TRUNCATE, and also,
why dont you do the updates in the DTS Transformation, maybe then you can
keep contrainsts
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:ei%23VHiguFHA.2620@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Ok. I'll try your idea anyway.
> I want to tell you how the DTS Package works:
> 1. Disable ALL contraint from all tables in a database
> 2. If success then continue to delete all the tables
> 3. Fill the deleted tables from another tables from another server
> 4. Update some values in certain tables
> Maybe you see something wrong in that work flow?
> Thanks
> Robert Lie
>
> David J. Cartwright wrote:
I have a problem with sql server jobs.
The jobs are executing DTS Package in scheculed manner.
The problem is the sometimes the schedule failed, and i don't know what
made the jobs failed.
And I have tried to trace it, but still coundn't find the problem.
Does anyone can help me out?
Thanks
Robert Lie
Try switching on Package logging in your DTS Packages. Right click in the
DTS Package, choose Package Properties and then Logging. When the job fails
again, you can then check the Package log (right-click the DTS Package in
Enterprise Manager, then choose package logs...). Hopefully you will find
the answer in there.
Jacco Schalkwijk
SQL Server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:%2397xWRfuFHA.2540@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I have a problem with sql server jobs.
> The jobs are executing DTS Package in scheculed manner.
> The problem is the sometimes the schedule failed, and i don't know what
> made the jobs failed.
> And I have tried to trace it, but still coundn't find the problem.
> Does anyone can help me out?
> Thanks
> Robert Lie
|||This is the error message when the job failed:
Executed as user: <domain>/<user>. ...un OnStart:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_6 DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart:
DTSStep_DTSDataPumpTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_4 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTS... Process
Exit Code -1073741819. The step failed.
Thanks
Robert Lie
Jacco Schalkwijk wrote:
> Try switching on Package logging in your DTS Packages. Right click in the
> DTS Package, choose Package Properties and then Logging. When the job fails
> again, you can then check the Package log (right-click the DTS Package in
> Enterprise Manager, then choose package logs...). Hopefully you will find
> the answer in there.
>
|||For the pump, you can set it to allow a certain number of errors, then log
these errors to a file, this should help you find what the pump is failing
on
If it is a Transform Data Task...Select The Properties..Then the Options
Tab...Enter an Exception File....Set Max Error Count to SOmething Like
9999...Run The Step...Review The Exception Log
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> This is the error message when the job failed:
> Executed as user: <domain>/<user>. ...un OnStart:
> DTSStep_DTSExecuteSQLTask_6 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_6
> DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10 DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_10 DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_4 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTSDataPumpTask_2 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_3 DTSRun OnStart: DTSStep_DTSDataPumpTask_2
> DTSRun OnStart: DTSStep_DTSDataPumpTask_3 DTSRun OnStart:
> DTSStep_DTSDataPumpTask_2 DTSRun OnStart: DTSStep_DTSDataPumpTask_3
> DTSRun OnStart: DTSStep_DTS... Process Exit Code -1073741819. The step
> failed.
>
> Thanks
> Robert Lie
> Jacco Schalkwijk wrote:
|||Ok. I'll try your idea anyway.
I want to tell you how the DTS Package works:
1. Disable ALL contraint from all tables in a database
2. If success then continue to delete all the tables
3. Fill the deleted tables from another tables from another server
4. Update some values in certain tables
Maybe you see something wrong in that work flow?
Thanks
Robert Lie
David J. Cartwright wrote:
> For the pump, you can set it to allow a certain number of errors, then log
> these errors to a file, this should help you find what the pump is failing
> on
> If it is a Transform Data Task...Select The Properties..Then the Options
> Tab...Enter an Exception File....Set Max Error Count to SOmething Like
> 9999...Run The Step...Review The Exception Log
> "Robert Lie" <robert.lie24@.gmail.com> wrote in message
> news:OrpONQguFHA.1472@.TK2MSFTNGP15.phx.gbl...
>
>
|||do you actualy delete/recreate the table, or do you use TRUNCATE, and also,
why dont you do the updates in the DTS Transformation, maybe then you can
keep contrainsts
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:ei%23VHiguFHA.2620@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Ok. I'll try your idea anyway.
> I want to tell you how the DTS Package works:
> 1. Disable ALL contraint from all tables in a database
> 2. If success then continue to delete all the tables
> 3. Fill the deleted tables from another tables from another server
> 4. Update some values in certain tables
> Maybe you see something wrong in that work flow?
> Thanks
> Robert Lie
>
> David J. Cartwright wrote:
Friday, February 24, 2012
JDBC with mulitple databases
Dear all,
Our application needs a bit of database redundancy.
Our application only accesses database for reading purposes.
We want to have two databases in separate machines. Incase one database
server dies the application should automatically extract data from the
other server.
Is there any JDBC driver available so that it can detect failure in the
main database server and then tries to extract data from the standby
database server?
Kind regards
--
Posted via http://dbforums.com
gbhatti wrote:
> Dear all,
> Our application needs a bit of database redundancy.
> Our application only accesses database for reading purposes.
> We want to have two databases in separate machines. Incase one database
> server dies the application should automatically extract data from the
> other server.
> Is there any JDBC driver available so that it can detect failure in the
> main database server and then tries to extract data from the standby
> database server?
> Kind regards
Not for SQLServer, but oracle has something like that if you have
oracle clustered DBMSes. However, it's not hard to write code
that will react to connectivity failure with one DBMS by connecting
to an alternate...
Joe Weinstein at BEA
> --
> Posted via http://dbforums.com|||"gbhatti" <member43992@.dbforums.com> wrote in message
news:3477901.1066098913@.dbforums.com...
> Dear all,
>
> Our application needs a bit of database redundancy.
>
> Our application only accesses database for reading purposes.
>
> We want to have two databases in separate machines. Incase one database
> server dies the application should automatically extract data from the
> other server.
>
> Is there any JDBC driver available so that it can detect failure in the
> main database server and then tries to extract data from the standby
> database server?
Not that I'm aware of. Typically this is done with SQL Enterprise in a
clustered format.
It is possible to encode it at the client level though also. But I'm not
aware of any JDBC driver that does it.
>
> Kind regards
>
> --
> Posted via http://dbforums.com
Monday, February 20, 2012
JDBC for MS SQL server
Dear all,
Where can I find JDBC for MS SQL server?
Thx for reply.
Victoria
Victoria wrote:
> Dear all,
> Where can I find JDBC for MS SQL server?
> Thx for reply.
> Victoria
go to microsoft.com and type jdbc in the search box?|||www.microsoft.com/sql
Neil Pike. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvfor...p?SRV=MSDevApps
(faqxxx.zip in lib 7)
or http://www.ntfaq.com/Articles/Index...epartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq
Subscribe to:
Posts (Atom)