Job succeeds manually but fails if scheduled

My client has a number of jobs that are run overnight. We've set them
up to email me when they're completed. Every morning I get in to a
bunch of emails like this:

<quote
JOB RUN:'Tech Pubs Email Notification' was run on 18/03/2006 at
00:00:00
DURATION:0 hours, 0 minutes, 0 seconds
STATUS: Succeeded
MESSAGES:The job succeeded. The Job was invoked by Schedule 10 (Send
Mail). The last step to run was step 1 (Send Mail).
</quote
However, the most important job - the database backup - fails every
time.

<quote>
JOB RUN:'DB Backup Job for DB Maintenance Plan 'DB Maintenance Plan1''
was run on 20/03/2006 at 18:00:00
DURATION:0 hours, 0 minutes, 2 seconds
STATUS: Failed
MESSAGES:The job failed. The Job was invoked by Schedule 7 (Schedule
1). The last step to run was step 1 (Step 1).
</quote
What's strange is that the job runs successfully if you kick it off
manually (in EM: right-click and "Start Job")!!! Does anyone have any
idea of why that might be? Where to look for diagnostic information?

TIA

Edwardteddysnips@.hotmail.com wrote:
> My client has a number of jobs that are run overnight. We've set them
> up to email me when they're completed. Every morning I get in to a
> bunch of emails like this:
> <quote>
> JOB RUN:'Tech Pubs Email Notification' was run on 18/03/2006 at
> 00:00:00
> DURATION:0 hours, 0 minutes, 0 seconds
> STATUS: Succeeded
> MESSAGES:The job succeeded. The Job was invoked by Schedule 10 (Send
> Mail). The last step to run was step 1 (Send Mail).
> </quote>
> However, the most important job - the database backup - fails every
> time.
> <quote>
> JOB RUN:'DB Backup Job for DB Maintenance Plan 'DB Maintenance Plan1''
> was run on 20/03/2006 at 18:00:00
> DURATION:0 hours, 0 minutes, 2 seconds
> STATUS: Failed
> MESSAGES:The job failed. The Job was invoked by Schedule 7 (Schedule
> 1). The last step to run was step 1 (Step 1).
> </quote>
> What's strange is that the job runs successfully if you kick it off
> manually (in EM: right-click and "Start Job")!!! Does anyone have any
> idea of why that might be? Where to look for diagnostic information?
> TIA
> Edward

Edward,

Have you got the right permissions?

This might sound a bit obvious but its usually the case. You might not
be the owner of the package and the system will only schedule the job
to run if the permissions are correct.

Bryan|||Bryan wrote:
> teddysnips@.hotmail.com wrote:
[...]
>
> Edward,
> Have you got the right permissions?
> This might sound a bit obvious but its usually the case. You might not
> be the owner of the package and the system will only schedule the job
> to run if the permissions are correct.
> Bryan

I would have assumed so, but I'll check. Thanks for the suggestion.

Edward|||Bryan wrote:
[...]
> Edward,
> Have you got the right permissions?
> This might sound a bit obvious but its usually the case. You might not
> be the owner of the package and the system will only schedule the job
> to run if the permissions are correct.

I checked on this today. All the jobs that run correctly have exactly
the same owners/permissions as the job that fails. I can't find any
attribute of the job (apart from what it actually does, obviously) that
distinguishes it from any of the other, successful jobs.

One other thing of which I was not aware. Apparently this job had been
scheduled successfully up until about a week ago, when it began
failing.

Any further thoughts/ideas?

TIA

Edward|||Hi Edward,

To be honest I don't ( I hate admitting defeat though....)

I have encountered this problem in the past especially when picking up
from any previous owners of packages.
One solution I have done is to copy the code from one package and dump
it into a package that is being allowed to run but with a different
owner.
This usually confirmed to myself that the problem must a a Owner /
Permission issue.

Apart from that I'm at a loss to recommend any other course of action.|||(teddysnips@.hotmail.com) writes:
> I checked on this today. All the jobs that run correctly have exactly
> the same owners/permissions as the job that fails. I can't find any
> attribute of the job (apart from what it actually does, obviously) that
> distinguishes it from any of the other, successful jobs.
> One other thing of which I was not aware. Apparently this job had been
> scheduled successfully up until about a week ago, when it began
> failing.
> Any further thoughts/ideas?

Check View History for the job. Don't miss to check View Step History.

Unfortunately, jobs that set up from a maintenance plan does not seem to
write very much useful information, so I'm not really expecting this to
give you anything. (But check nevertheless.) I the maintenance plan has
its own log somewhere, but I don't remember where - or if there was anything
that useful in it.

May you should scrap the plan, and set up the jobs without it.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||<teddysnips@.hotmail.com> wrote in message
news:1142932717.825816.151430@.z34g2000cwc.googlegr oups.com...
> My client has a number of jobs that are run overnight. We've set them
> up to email me when they're completed. Every morning I get in to a
> bunch of emails like this:
> <quote>
> JOB RUN: 'Tech Pubs Email Notification' was run on 18/03/2006 at
> 00:00:00
> DURATION: 0 hours, 0 minutes, 0 seconds
> STATUS: Succeeded
> MESSAGES: The job succeeded. The Job was invoked by Schedule 10 (Send
> Mail). The last step to run was step 1 (Send Mail).
> </quote>
> However, the most important job - the database backup - fails every
> time.
> <quote>
> JOB RUN: 'DB Backup Job for DB Maintenance Plan 'DB Maintenance Plan1''
> was run on 20/03/2006 at 18:00:00
> DURATION: 0 hours, 0 minutes, 2 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 7 (Schedule
> 1). The last step to run was step 1 (Step 1).
> </quote>
> What's strange is that the job runs successfully if you kick it off
> manually (in EM: right-click and "Start Job")!!! Does anyone have any
> idea of why that might be? Where to look for diagnostic information?
> TIA
> Edward

If it isn't the owner of the job step (sa would be good if sa owns the
database), then check for proper disk
space in the backup destination.

Job Notification

On our SQL 2000 server there is no MAPI client or Outlook installed. The NET SEND command has been disabled on the server/network. The xp_sendmail can not be used due to SQL Mail not started due to no Outlook profile. I don't find that the Notification pa
ge allows to attach a command or batch file to do this job. It is just writing the Log to Application Event Log. Any feedback would be appreciated.
There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.
|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:

> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>
|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thanks...Fraz
"Richard Ding" wrote:

> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>
|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz[vbcol=seagreen]
> "Richard Ding" wrote:
sql

Job Notification

On our SQL 2000 server there is no MAPI client or Outlook installed. The NET
SEND command has been disabled on the server/network. The xp_sendmail can n
ot be used due to SQL Mail not started due to no Outlook profile. I don't fi
nd that the Notification pa
ge allows to attach a command or batch file to do this job. It is just writi
ng the Log to Application Event Log. Any feedback would be appreciated.There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdo
sysmail in the Master database but could find them. Could you please let me
know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:

> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me
know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thank
s...Fraz
"Richard Ding" wrote:

> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmai
l in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks.
.Fraz[vbcol=seagreen]
> "Richard Ding" wrote:
>

Job Notification

On our SQL 2000 server there is no MAPI client or Outlook installed. The NET SEND command has been disabled on the server/network. The xp_sendmail can not be used due to SQL Mail not started due to no Outlook profile. I don't find that the Notification page allows to attach a command or batch file to do this job. It is just writing the Log to Application Event Log. Any feedback would be appreciated.Check out SMTPMail on SQLDev.NET. You can either add that
as a job step on failure, or create a job that is called
when an alert executes. I believe there is an example of
the latter on that website.
FYI, SQL 2005 is going to support both MAPI-based and SMTP-
based email notification.
>--Original Message--
>On our SQL 2000 server there is no MAPI client or Outlook
installed. The NET SEND command has been disabled on the
server/network. The xp_sendmail can not be used due to SQL
Mail not started due to no Outlook profile. I don't find
that the Notification page allows to attach a command or
batch file to do this job. It is just writing the Log to
Application Event Log. Any feedback would be appreciated.
>.
>|||There're about three ways to email a notification for a job:
1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
2. Install xp_smtp_mail and it's dll to bypass MAPI.
3. Install sp_send_cdosysmail and use this stored procedure to send out
email.
I personally prefer sqlmail due to it's rich features. But be aware of its
total dependency on MS Exchange.
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> On our SQL 2000 server there is no MAPI client or Outlook installed. The
NET SEND command has been disabled on the server/network. The xp_sendmail
can not be used due to SQL Mail not started due to no Outlook profile. I
don't find that the Notification page allows to attach a command or batch
file to do this job. It is just writing the Log to Application Event Log.
Any feedback would be appreciated.|||Hello Richard,
Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Hello Richard: Thanks for your feedback. Will appreciate if you could let me know where I can find xp_smtp_mail and sp_send_cdosysmail procedures. Thanks...Fraz
"Richard Ding" wrote:
> There're about three ways to email a notification for a job:
> 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> 3. Install sp_send_cdosysmail and use this stored procedure to send out
> email.
> I personally prefer sqlmail due to it's rich features. But be aware of its
> total dependency on MS Exchange.
>
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> NET SEND command has been disabled on the server/network. The xp_sendmail
> can not be used due to SQL Mail not started due to no Outlook profile. I
> don't find that the Notification page allows to attach a command or batch
> file to do this job. It is just writing the Log to Application Event Log.
> Any feedback would be appreciated.
>
>|||Below might be useful:
http://www.karaszi.com/SQLServer/info_no_mapi.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:1858581C-7207-4788-B9D3-5C02874DB8A3@.microsoft.com...
> Hello Richard,
> Thanks for your valuable feedback. I looked for xp_smtp_mail and sp_send_cdosysmail in the Master database
but could find them. Could you please let me know where I can find these procedures. Thanks...Fraz
> "Richard Ding" wrote:
> > There're about three ways to email a notification for a job:
> > 1. Install MAPI and Outlook to have SQLMAIL work together with Exchange.
> > 2. Install xp_smtp_mail and it's dll to bypass MAPI.
> > 3. Install sp_send_cdosysmail and use this stored procedure to send out
> > email.
> >
> > I personally prefer sqlmail due to it's rich features. But be aware of its
> > total dependency on MS Exchange.
> >
> >
> > "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> > news:55D6ACD2-73BC-46F9-894B-8F1F9F4DC4C2@.microsoft.com...
> > > On our SQL 2000 server there is no MAPI client or Outlook installed. The
> > NET SEND command has been disabled on the server/network. The xp_sendmail
> > can not be used due to SQL Mail not started due to no Outlook profile. I
> > don't find that the Notification page allows to attach a command or batch
> > file to do this job. It is just writing the Log to Application Event Log.
> > Any feedback would be appreciated.
> >
> >
> >

JDBC Driver for SQL 2000 - Pls help

One of the applications "Epistemic" which my client is using needs a JDBC 3.0
Compliant driver to connection to out SQL Server 2000 instance
Questions
1. Is this driver available in installation of client software for SQL
Server 2000, if not where can i get it
2. Like for ODBC we set up a profile in ODBC administrator, what do we do
for JDBC
3. Will accessing SQL 2000 through JDBC drive be any slower than using OLEDB
which is the default connectivity software for SQL Server 2000
Thanks
Hi
The Microsoft driver is a type 4 driver and downloadable from
http://www.microsoft.com/downloads/d...displaylang=en
the included help and readme files show how it should be used.
For other options look at
http://servlet.java.sun.com/products...ers/index.html
You may also want to check the posts in microsoft.public.sqlserver.jdbcdriver.
John
"Sanjay" wrote:

> One of the applications "Epistemic" which my client is using needs a JDBC 3.0
> Compliant driver to connection to out SQL Server 2000 instance
> Questions
> 1. Is this driver available in installation of client software for SQL
> Server 2000, if not where can i get it
> 2. Like for ODBC we set up a profile in ODBC administrator, what do we do
> for JDBC
> 3. Will accessing SQL 2000 through JDBC drive be any slower than using OLEDB
> which is the default connectivity software for SQL Server 2000
> Thanks
>
|||Sanjay wrote:
> One of the applications "Epistemic" which my client is using needs a
JDBC 3.0
> Compliant driver to connection to out SQL Server 2000 instance
> Questions
> 1. Is this driver available in installation of client software for
SQL
> Server 2000, if not where can i get it
The Microsoft driver is only a JDBC 2.0 implementation and it has a
number of problems, ranging from stability to performance, in which you
seem to be interested. E.g. if you need transaction support (which you
probably do) the MS driver will use server side cursors and will make a
request for each row you retrieve on a SELECT.

> 2. Like for ODBC we set up a profile in ODBC administrator, what do
we do
> for JDBC
Nothing, just drop the jar in the classpath and configure the URL in
your application.

> 3. Will accessing SQL 2000 through JDBC drive be any slower than
using OLEDB
> which is the default connectivity software for SQL Server 2000
With the MS driver, probably so. Try jTDS (
http://jtds.sourceforge.net/ ) instead. It's a JDBC 3.0 implementation,
it's way more stable than the MS driver and as fast as OLEDB.
Alin,
The jTDS Project.
Disclaimer: I am a jTDS developer so my views might not be totally
objective.

JDBC Driver for SQL 2000 - Pls help

One of the applications "Epistemic" which my client is using needs a JDBC 3.0
Compliant driver to connection to out SQL Server 2000 instance
Questions
1. Is this driver available in installation of client software for SQL
Server 2000, if not where can i get it
2. Like for ODBC we set up a profile in ODBC administrator, what do we do
for JDBC
3. Will accessing SQL 2000 through JDBC drive be any slower than using OLEDB
which is the default connectivity software for SQL Server 2000
ThanksHi
The Microsoft driver is a type 4 driver and downloadable from
http://www.microsoft.com/downloads/details.aspx?FamilyID=07287B11-0502-461A-B138-2AA54BFDC03A&displaylang=en
the included help and readme files show how it should be used.
For other options look at
http://servlet.java.sun.com/products/jdbc/drivers/index.html
You may also want to check the posts in microsoft.public.sqlserver.jdbcdriver.
John
"Sanjay" wrote:
> One of the applications "Epistemic" which my client is using needs a JDBC 3.0
> Compliant driver to connection to out SQL Server 2000 instance
> Questions
> 1. Is this driver available in installation of client software for SQL
> Server 2000, if not where can i get it
> 2. Like for ODBC we set up a profile in ODBC administrator, what do we do
> for JDBC
> 3. Will accessing SQL 2000 through JDBC drive be any slower than using OLEDB
> which is the default connectivity software for SQL Server 2000
> Thanks
>|||Sanjay wrote:
> One of the applications "Epistemic" which my client is using needs a
JDBC 3.0
> Compliant driver to connection to out SQL Server 2000 instance
> Questions
> 1. Is this driver available in installation of client software for
SQL
> Server 2000, if not where can i get it
The Microsoft driver is only a JDBC 2.0 implementation and it has a
number of problems, ranging from stability to performance, in which you
seem to be interested. E.g. if you need transaction support (which you
probably do) the MS driver will use server side cursors and will make a
request for each row you retrieve on a SELECT.
> 2. Like for ODBC we set up a profile in ODBC administrator, what do
we do
> for JDBC
Nothing, just drop the jar in the classpath and configure the URL in
your application.
> 3. Will accessing SQL 2000 through JDBC drive be any slower than
using OLEDB
> which is the default connectivity software for SQL Server 2000
With the MS driver, probably so. Try jTDS (
http://jtds.sourceforge.net/ ) instead. It's a JDBC 3.0 implementation,
it's way more stable than the MS driver and as fast as OLEDB.
Alin,
The jTDS Project.
Disclaimer: I am a jTDS developer so my views might not be totally
objective.

JDBC Driver for SQL 2000 - Pls help

One of the applications "Epistemic" which my client is using needs a JDBC 3.
0
Compliant driver to connection to out SQL Server 2000 instance
Questions
1. Is this driver available in installation of client software for SQL
Server 2000, if not where can i get it
2. Like for ODBC we set up a profile in ODBC administrator, what do we do
for JDBC
3. Will accessing SQL 2000 through JDBC drive be any slower than using OLEDB
which is the default connectivity software for SQL Server 2000
ThanksHi
The Microsoft driver is a type 4 driver and downloadable from
http://www.microsoft.com/downloads/...&displaylang=en
the included help and readme files show how it should be used.
For other options look at
http://servlet.java.sun.com/product...vers/index.html
You may also want to check the posts in microsoft.public.sqlserver.jdbcdrive
r.
John
"Sanjay" wrote:

> One of the applications "Epistemic" which my client is using needs a JDBC
3.0
> Compliant driver to connection to out SQL Server 2000 instance
> Questions
> 1. Is this driver available in installation of client software for SQL
> Server 2000, if not where can i get it
> 2. Like for ODBC we set up a profile in ODBC administrator, what do we do
> for JDBC
> 3. Will accessing SQL 2000 through JDBC drive be any slower than using OLE
DB
> which is the default connectivity software for SQL Server 2000
> Thanks
>|||Sanjay wrote:
> One of the applications "Epistemic" which my client is using needs a
JDBC 3.0
> Compliant driver to connection to out SQL Server 2000 instance
> Questions
> 1. Is this driver available in installation of client software for
SQL
> Server 2000, if not where can i get it
The Microsoft driver is only a JDBC 2.0 implementation and it has a
number of problems, ranging from stability to performance, in which you
seem to be interested. E.g. if you need transaction support (which you
probably do) the MS driver will use server side cursors and will make a
request for each row you retrieve on a SELECT.

> 2. Like for ODBC we set up a profile in ODBC administrator, what do
we do
> for JDBC
Nothing, just drop the jar in the classpath and configure the URL in
your application.

> 3. Will accessing SQL 2000 through JDBC drive be any slower than
using OLEDB
> which is the default connectivity software for SQL Server 2000
With the MS driver, probably so. Try jTDS (
http://jtds.sourceforge.net/ ) instead. It's a JDBC 3.0 implementation,
it's way more stable than the MS driver and as fast as OLEDB.
Alin,
The jTDS Project.
Disclaimer: I am a jTDS developer so my views might not be totally
objective.