job execution

Greetings.

We generate table exports on a SQL Server 2005 instance at irregular intervals. Often when exports are required we have a number of them that need to be run. We've found that the exports job run sequentially. Is there a way of simultaneously executing the jobs ?

Thanks.

alan

If you are referring to several steps in a SQL Agent Job, then they always run sequentially. You could make a separate Job for each of the steps, and, depending upon your server hardware and the user activity, they may then run in parallel.

You could create a DTS (SQL 2000) or SSIS (SQL 2005) package, and in the package you could easily extablish that the various 'steps' were to run in parallel.

|||

Very helpful.

Thank you.

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.