RUN SQL 2005 SSIS Package on SQL 2000 BOXES?

I have a package designed and working correctly for months now. My challenge now is to run this package on a box that does not have SQL 2005 SSIS install. It has SQL 2000 installed.

My question is - Can I compile the SSIS into EXE or any other kind of DTS package to run on a none-SQL 2005 box?

Thanks!

--Jon

You don't need ANY version of SQL Server (i.e. the database engine) installed in order to run a SSIS package. You just need SSIS installed.

And no, its not possible to run it without having SSIS installed. That's what you pay the money for.

-Jamie

Run Single Step In Job on SQL Server 2000

I am working in an environment where application devs don't have the
ability to run SQL Server Jobs that are setup already in production.
Our jobs are multi-step and have a lot of steps. What I am looking for
is a way for the operators who have privileges in production but know
nothing about SQL Server to run a single step inside of a job without
triggering other steps. SQL Server 2000 allows for the ability to
start a job at a certain step but what I want to happen is for only
that particular step to run. Any thoughts?
SpencerBecause of the seperation of duties in the organization I am also
looking at creating an "On Demand" job that application devs will have
privileges to update a particular .sql file and then put in a runsheet
to have operations kick off the on demand job. What I do want the on
demand job to do however is do some logging such as who kicked the job
off, what sql ended up being executed, rows affected, etc. Maybe an
email as well. I know there have got to be lots of environments doing
something similar.
Spencer|||On 11 May 2006 18:21:08 -0700, "stabbert" <spencer@.tabbert.net> wrote:
>I am working in an environment where application devs don't have the
>ability to run SQL Server Jobs that are setup already in production.
>Our jobs are multi-step and have a lot of steps. What I am looking for
>is a way for the operators who have privileges in production but know
>nothing about SQL Server to run a single step inside of a job without
>triggering other steps. SQL Server 2000 allows for the ability to
>start a job at a certain step but what I want to happen is for only
>that particular step to run. Any thoughts?
>Spencer
It's possible to create code that parses out the job step and creates
a new job that you can then run immediately, but short of something
zippy like this, I don't know how else you could do it.
Josh

Run Single Step In Job on SQL Server 2000

I am working in an environment where application devs don't have the
ability to run SQL Server Jobs that are setup already in production.
Our jobs are multi-step and have a lot of steps. What I am looking for
is a way for the operators who have privileges in production but know
nothing about SQL Server to run a single step inside of a job without
triggering other steps. SQL Server 2000 allows for the ability to
start a job at a certain step but what I want to happen is for only
that particular step to run. Any thoughts?
SpencerBecause of the seperation of duties in the organization I am also
looking at creating an "On Demand" job that application devs will have
privileges to update a particular .sql file and then put in a runsheet
to have operations kick off the on demand job. What I do want the on
demand job to do however is do some logging such as who kicked the job
off, what sql ended up being executed, rows affected, etc. Maybe an
email as well. I know there have got to be lots of environments doing
something similar.
Spencer|||On 11 May 2006 18:21:08 -0700, "stabbert" <spencer@.tabbert.net> wrote:
>I am working in an environment where application devs don't have the
>ability to run SQL Server Jobs that are setup already in production.
>Our jobs are multi-step and have a lot of steps. What I am looking for
>is a way for the operators who have privileges in production but know
>nothing about SQL Server to run a single step inside of a job without
>triggering other steps. SQL Server 2000 allows for the ability to
>start a job at a certain step but what I want to happen is for only
>that particular step to run. Any thoughts?
>Spencer
It's possible to create code that parses out the job step and creates
a new job that you can then run immediately, but short of something
zippy like this, I don't know how else you could do it.
Josh

run both enterprise and msde on same box

Is it possible to run both MSDE and enterprise edition (sql server 2000)
on the same box?
I am working on an application that will include MSDE, and I'd like to
test it on my developing machine that is already running Enterprise. I
could just shut off Enterprise, but the MSDE needs to be a subscriber,
so they both need to be running.
Thanks,
-Casey
hi,
C Williams wrote:
> Is it possible to run both MSDE and enterprise edition (sql server
> 2000) on the same box?
> I am working on an application that will include MSDE, and I'd like to
> test it on my developing machine that is already running Enterprise. I
> could just shut off Enterprise, but the MSDE needs to be a
> subscriber, so they both need to be running.
yes, it can be done..
up to 16 instances can be installed on the very same machine, resources
permitting :D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply