Job runs succesfully, but database not updated

I have created a job to run an executable. This executable has to read an
Excelsheet in order to import the data into the database.
I got the message that the job has run succesfully, but the data is not in
the database.
My job looks like this:
c:\mydirectory\bin\excelimport.exe /Slocal) /D:DataComp 20051020
S: --> the local server
D:--> database name
Thank you for your help.
Kind regards,
LoHi
You don't say where the job expects the excel file to be! Have you looks at
SQL profiler to see what is happening when the program runs?
John
"lo" wrote:

> I have created a job to run an executable. This executable has to read an
> Excelsheet in order to import the data into the database.
> I got the message that the job has run succesfully, but the data is not in
> the database.
> My job looks like this:
> c:\mydirectory\bin\excelimport.exe /Slocal) /D:DataComp 20051020
> S: --> the local server
> D:--> database name
> --
> Thank you for your help.
> Kind regards,
> Lo|||I have run the profiler, but here as well I get no error message once or eve
r.
I have updated the string like this
c:\mydirectory\bin\excelimport.exe /Slocal) /D:[DataComp 20051020]
The path to the excel sheet is in the excelimport.exe.
Do you have any other idea'
Thank you for your help.
Kind regards,
Lo
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You don't say where the job expects the excel file to be! Have you looks a
t
> SQL profiler to see what is happening when the program runs?
> John
> "lo" wrote:
>|||Hi
I would not expect any error messages from SQL Profile, just the information
about which database it is running against and what SQL statements are being
executed by the job. You can then confirm that it is not connecting to the
correct database or that it is not finding the file.
Do you have a dynamic properties task to change the destination database?
You may want to see http://www.sqldts.com/default.aspx?252
John
"lo" wrote:
[vbcol=seagreen]
> I have run the profiler, but here as well I get no error message once or e
ver.
> I have updated the string like this
> c:\mydirectory\bin\excelimport.exe /Slocal) /D:[DataComp 20051020]
> The path to the excel sheet is in the excelimport.exe.
> Do you have any other idea'
>
> --
> Thank you for your help.
> Kind regards,
> Lo
>
> "John Bell" wrote:
>

Job runs succesfully, but database not updated

I have created a job to run an executable. This executable has to read an
Excelsheet in order to import the data into the database.
I got the message that the job has run succesfully, but the data is not in
the database.
My job looks like this:
c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
S: --> the local server
D:--> database name
--
Thank you for your help.
Kind regards,
LoHi
You don't say where the job expects the excel file to be! Have you looks at
SQL profiler to see what is happening when the program runs?
John
"lo" wrote:
> I have created a job to run an executable. This executable has to read an
> Excelsheet in order to import the data into the database.
> I got the message that the job has run succesfully, but the data is not in
> the database.
> My job looks like this:
> c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
> S: --> the local server
> D:--> database name
> --
> Thank you for your help.
> Kind regards,
> Lo|||I have run the profiler, but here as well I get no error message once or ever.
I have updated the string like this
c:\mydirectory\bin\excelimport.exe /S:(local) /D:[DataComp 20051020]
The path to the excel sheet is in the excelimport.exe.
Do you have any other idea'
Thank you for your help.
Kind regards,
Lo
"John Bell" wrote:
> Hi
> You don't say where the job expects the excel file to be! Have you looks at
> SQL profiler to see what is happening when the program runs?
> John
> "lo" wrote:
> > I have created a job to run an executable. This executable has to read an
> > Excelsheet in order to import the data into the database.
> > I got the message that the job has run succesfully, but the data is not in
> > the database.
> > My job looks like this:
> > c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
> > S: --> the local server
> > D:--> database name
> >
> > --
> > Thank you for your help.
> >
> > Kind regards,
> >
> > Lo|||Hi
I would not expect any error messages from SQL Profile, just the information
about which database it is running against and what SQL statements are being
executed by the job. You can then confirm that it is not connecting to the
correct database or that it is not finding the file.
Do you have a dynamic properties task to change the destination database?
You may want to see http://www.sqldts.com/default.aspx?252
John
"lo" wrote:
> I have run the profiler, but here as well I get no error message once or ever.
> I have updated the string like this
> c:\mydirectory\bin\excelimport.exe /S:(local) /D:[DataComp 20051020]
> The path to the excel sheet is in the excelimport.exe.
> Do you have any other idea'
>
> --
> Thank you for your help.
> Kind regards,
> Lo
>
> "John Bell" wrote:
> > Hi
> >
> > You don't say where the job expects the excel file to be! Have you looks at
> > SQL profiler to see what is happening when the program runs?
> >
> > John
> >
> > "lo" wrote:
> >
> > > I have created a job to run an executable. This executable has to read an
> > > Excelsheet in order to import the data into the database.
> > > I got the message that the job has run succesfully, but the data is not in
> > > the database.
> > > My job looks like this:
> > > c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
> > > S: --> the local server
> > > D:--> database name
> > >
> > > --
> > > Thank you for your help.
> > >
> > > Kind regards,
> > >
> > > Lo

Job Failure

From the job history, we find that a scheduled job has failed after we have
updated the structure of some tables.
We would like to know what is the best way to find out what causes the
failure ? Is there any built-in error log ?
ThanksJason,
In SQLAgent, right click the job and select View Job History..., tick
the show step details checkbox at the top right. Navigate to the step
that failed and the error message should present itself in the bottom pane.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Jason wrote:
> From the job history, we find that a scheduled job has failed after we have
> updated the structure of some tables.
> We would like to know what is the best way to find out what causes the
> failure ? Is there any built-in error log ?
> Thanks
>|||The job is written by consultant. From memory, the message is something
like "It takes xx second to finish Task 1. It takes yy seconds to finish
Task 2. ...... Job failed".
Jason
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
> Jason,
> In SQLAgent, right click the job and select View Job History..., tick the
> show step details checkbox at the top right. Navigate to the step that
> failed and the error message should present itself in the bottom pane.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
>
> Jason wrote:
>> From the job history, we find that a scheduled job has failed after we
>> have updated the structure of some tables.
>> We would like to know what is the best way to find out what causes the
>> failure ? Is there any built-in error log ?
>> Thanks|||"Show step details" checkbox. This is essential!
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jason" <anonymous@.discussions.microsoft.com> wrote in message
news:OtaCYYqYFHA.1028@.TK2MSFTNGP10.phx.gbl...
> The job is written by consultant. From memory, the message is something like "It takes xx second
> to finish Task 1. It takes yy seconds to finish Task 2. ...... Job failed".
> Jason
> "Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
> news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
>> Jason,
>> In SQLAgent, right click the job and select View Job History..., tick the show step details
>> checkbox at the top right. Navigate to the step that failed and the error message should present
>> itself in the bottom pane.
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602m.html
>>
>>
>> Jason wrote:
>> From the job history, we find that a scheduled job has failed after we have updated the
>> structure of some tables.
>> We would like to know what is the best way to find out what causes the failure ? Is there any
>> built-in error log ?
>> Thanks
>|||Dear Tibor and Mark,
Thank you for your advice.
There is only 1 step. It seems that the contractor has written the message
out after finishing each step. In this way, it says "It takes xxx seconds
to finish Task 1 .. etc". However, since there are too many Tasks (around
150), in this way, at the last row, it shows "dot dot dot Job Failed" but I
am not able to see clearly which Task fails.
Thanking you in anticipation.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uEvUcdqYFHA.2588@.TK2MSFTNGP14.phx.gbl...
> "Show step details" checkbox. This is essential!
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Jason" <anonymous@.discussions.microsoft.com> wrote in message
> news:OtaCYYqYFHA.1028@.TK2MSFTNGP10.phx.gbl...
>> The job is written by consultant. From memory, the message is something
>> like "It takes xx second to finish Task 1. It takes yy seconds to finish
>> Task 2. ...... Job failed".
>> Jason
>> "Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
>> news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
>> Jason,
>> In SQLAgent, right click the job and select View Job History..., tick
>> the show step details checkbox at the top right. Navigate to the step
>> that failed and the error message should present itself in the bottom
>> pane.
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602m.html
>>
>>
>> Jason wrote:
>> From the job history, we find that a scheduled job has failed after we
>> have updated the structure of some tables.
>> We would like to know what is the best way to find out what causes the
>> failure ? Is there any built-in error log ?
>> Thanks
>>
>|||Hi,
Try to look if external log has been turned on or not.
Go to the job's properties, choose the step, click 'Edit'
then choose 'Advanced' tab.
There would be 'Output file' field.
Check if it is set and if it is, then look at the file.
Regards.
"Jason" wrote:
> Dear Tibor and Mark,
> Thank you for your advice.
> There is only 1 step. It seems that the contractor has written the message
> out after finishing each step. In this way, it says "It takes xxx seconds
> to finish Task 1 .. etc". However, since there are too many Tasks (around
> 150), in this way, at the last row, it shows "dot dot dot Job Failed" but I
> am not able to see clearly which Task fails.
> Thanking you in anticipation.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:uEvUcdqYFHA.2588@.TK2MSFTNGP14.phx.gbl...
> > "Show step details" checkbox. This is essential!
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Jason" <anonymous@.discussions.microsoft.com> wrote in message
> > news:OtaCYYqYFHA.1028@.TK2MSFTNGP10.phx.gbl...
> >> The job is written by consultant. From memory, the message is something
> >> like "It takes xx second to finish Task 1. It takes yy seconds to finish
> >> Task 2. ...... Job failed".
> >>
> >> Jason
> >>
> >> "Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
> >> news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
> >> Jason,
> >>
> >> In SQLAgent, right click the job and select View Job History..., tick
> >> the show step details checkbox at the top right. Navigate to the step
> >> that failed and the error message should present itself in the bottom
> >> pane.
> >>
> >> --
> >> Mark Allison, SQL Server MVP
> >> http://www.markallison.co.uk
> >>
> >> Looking for a SQL Server replication book?
> >> http://www.nwsu.com/0974973602m.html
> >>
> >>
> >>
> >>
> >>
> >> Jason wrote:
> >> From the job history, we find that a scheduled job has failed after we
> >> have updated the structure of some tables.
> >>
> >> We would like to know what is the best way to find out what causes the
> >> failure ? Is there any built-in error log ?
> >>
> >> Thanks
> >>
> >>
> >
> >
>
>|||How about setting *in the job step* to output to a file? You can then open the file and see where
you get error messages etc.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jason" <anonymous@.discussions.microsoft.com> wrote in message
news:%23apBohqYFHA.3032@.TK2MSFTNGP10.phx.gbl...
> Dear Tibor and Mark,
> Thank you for your advice.
> There is only 1 step. It seems that the contractor has written the message out after finishing
> each step. In this way, it says "It takes xxx seconds to finish Task 1 .. etc". However, since
> there are too many Tasks (around 150), in this way, at the last row, it shows "dot dot dot Job
> Failed" but I am not able to see clearly which Task fails.
> Thanking you in anticipation.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uEvUcdqYFHA.2588@.TK2MSFTNGP14.phx.gbl...
>> "Show step details" checkbox. This is essential!
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Jason" <anonymous@.discussions.microsoft.com> wrote in message
>> news:OtaCYYqYFHA.1028@.TK2MSFTNGP10.phx.gbl...
>> The job is written by consultant. From memory, the message is something like "It takes xx
>> second to finish Task 1. It takes yy seconds to finish Task 2. ...... Job failed".
>> Jason
>> "Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
>> news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
>> Jason,
>> In SQLAgent, right click the job and select View Job History..., tick the show step details
>> checkbox at the top right. Navigate to the step that failed and the error message should
>> present itself in the bottom pane.
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602m.html
>>
>>
>> Jason wrote:
>> From the job history, we find that a scheduled job has failed after we have updated the
>> structure of some tables.
>> We would like to know what is the best way to find out what causes the failure ? Is there any
>> built-in error log ?
>> Thanks
>>
>>
>|||Hi,
I find that there is no external log is enabled. I would like to follow
your suggestion. Where is the best place to put the external log ? I don't
want to mix it with other logs.
Thanks
"SkyWalker" <SkyWalker@.discussions.microsoft.com> wrote in message
news:DEA5C8F3-F87E-4707-8F2D-5406C86A7F19@.microsoft.com...
> Hi,
> Try to look if external log has been turned on or not.
> Go to the job's properties, choose the step, click 'Edit'
> then choose 'Advanced' tab.
> There would be 'Output file' field.
> Check if it is set and if it is, then look at the file.
> Regards.
> "Jason" wrote:
>> Dear Tibor and Mark,
>> Thank you for your advice.
>> There is only 1 step. It seems that the contractor has written the
>> message
>> out after finishing each step. In this way, it says "It takes xxx
>> seconds
>> to finish Task 1 .. etc". However, since there are too many Tasks
>> (around
>> 150), in this way, at the last row, it shows "dot dot dot Job Failed" but
>> I
>> am not able to see clearly which Task fails.
>> Thanking you in anticipation.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in
>> message news:uEvUcdqYFHA.2588@.TK2MSFTNGP14.phx.gbl...
>> > "Show step details" checkbox. This is essential!
>> >
>> > --
>> > Tibor Karaszi, SQL Server MVP
>> > http://www.karaszi.com/sqlserver/default.asp
>> > http://www.solidqualitylearning.com/
>> >
>> >
>> > "Jason" <anonymous@.discussions.microsoft.com> wrote in message
>> > news:OtaCYYqYFHA.1028@.TK2MSFTNGP10.phx.gbl...
>> >> The job is written by consultant. From memory, the message is
>> >> something
>> >> like "It takes xx second to finish Task 1. It takes yy seconds to
>> >> finish
>> >> Task 2. ...... Job failed".
>> >>
>> >> Jason
>> >>
>> >> "Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
>> >> news:eMd$pWqYFHA.580@.TK2MSFTNGP15.phx.gbl...
>> >> Jason,
>> >>
>> >> In SQLAgent, right click the job and select View Job History..., tick
>> >> the show step details checkbox at the top right. Navigate to the step
>> >> that failed and the error message should present itself in the bottom
>> >> pane.
>> >>
>> >> --
>> >> Mark Allison, SQL Server MVP
>> >> http://www.markallison.co.uk
>> >>
>> >> Looking for a SQL Server replication book?
>> >> http://www.nwsu.com/0974973602m.html
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Jason wrote:
>> >> From the job history, we find that a scheduled job has failed after
>> >> we
>> >> have updated the structure of some tables.
>> >>
>> >> We would like to know what is the best way to find out what causes
>> >> the
>> >> failure ? Is there any built-in error log ?
>> >>
>> >> Thanks
>> >>
>> >>
>> >
>> >
>>

JDBC driver for SQL Server 2000 and Java 5?

How can I get a copy of an updated JDBC driver that works with Java 5 (for
SQL Server 2000)? I need to upgrade my software to run on the latest Java
runtime soon...
Tim O'Konski wrote:
> How can I get a copy of an updated JDBC driver that works with Java 5
(for
> SQL Server 2000)? I need to upgrade my software to run on the latest
Java
> runtime soon...
Your old driver will work just fine with Java 5. Apart from a very
misterious _possible issue_ that noone knows nothing about:
http://groups-beta.google.com/group/...54c78ec924fc65
Alin.
|||Microsoft SQL Server 2000 Driver for JDBC SP3 has now been certified
against Java 1.5. We did not see any regression with the BigDecimal
issue.
-shelby
Shelby Goerlitz
Microsoft, SQL Server
"Alin Sinpalean" <alin@.earthling.net> wrote in message
news:alin@.earthling.net:
> Tim O'Konski wrote:
>
> (for
>
> Java
>
> Your old driver will work just fine with Java 5. Apart from a very
> misterious _possible issue_ that noone knows nothing about:
> http://groups-beta.google.com/group/...jdbcdriver/br
> owse_thread/thread/bc54c78ec924fc65
> Alin.