Control-M vs SQL Server Agent

Hi
We have a plan to migrate from SQL Server Agent to Control for job schedulin
g.
For those who have done this or attempted to it, I would be very grateful if
you could share some of your experience.
I would be interested in:
- Which scripting language did you use for wrapper scripts?
- Did you continue using maintenance plans for backups, dbcc's, re-indixing,
etc.?
- How did you run dts packages from control-M and were you able to report
useful message through control-M?
- Why would you, or would you not, migrate to control-M
Many thanks,Hi
We are at a start of a 300 SQL Server 2000 migration project to Control-M.
It is the corporate standard, so we don't have much choice.
We will probably use PERL for the wrappers, but VBS might still be used.
Everything will be migrated, but we have a toolset of PERL scripts that does
backups, restores, cold loads etc. This will help a lot.
The DTS stuff, well, it will be moved, but I don't think we will get good
error reporting out of it, unless each DTS package logs what it is doing.
In 60 days, we have to be finished.....
Regards
Mike
"dave222" wrote:

> Hi
> We have a plan to migrate from SQL Server Agent to Control for job schedul
ing.
> For those who have done this or attempted to it, I would be very grateful
if
> you could share some of your experience.
> I would be interested in:
> - Which scripting language did you use for wrapper scripts?
> - Did you continue using maintenance plans for backups, dbcc's, re-indixin
g,
> etc.?
> - How did you run dts packages from control-M and were you able to report
> useful message through control-M?
> - Why would you, or would you not, migrate to control-M
> Many thanks,

Control-M vs SQL Server Agent

Hi
We have a plan to migrate from SQL Server Agent to Control for job scheduling.
For those who have done this or attempted to it, I would be very grateful if
you could share some of your experience.
I would be interested in:
- Which scripting language did you use for wrapper scripts?
- Did you continue using maintenance plans for backups, dbcc's, re-indixing,
etc.?
- How did you run dts packages from control-M and were you able to report
useful message through control-M?
- Why would you, or would you not, migrate to control-M
Many thanks,Hi
We are at a start of a 300 SQL Server 2000 migration project to Control-M.
It is the corporate standard, so we don't have much choice.
We will probably use Perl for the wrappers, but VBS might still be used.
Everything will be migrated, but we have a toolset of Perl scripts that does
backups, restores, cold loads etc. This will help a lot.
The DTS stuff, well, it will be moved, but I don't think we will get good
error reporting out of it, unless each DTS package logs what it is doing.
In 60 days, we have to be finished.....
Regards
Mike
"dave222" wrote:
> Hi
> We have a plan to migrate from SQL Server Agent to Control for job scheduling.
> For those who have done this or attempted to it, I would be very grateful if
> you could share some of your experience.
> I would be interested in:
> - Which scripting language did you use for wrapper scripts?
> - Did you continue using maintenance plans for backups, dbcc's, re-indixing,
> etc.?
> - How did you run dts packages from control-M and were you able to report
> useful message through control-M?
> - Why would you, or would you not, migrate to control-M
> Many thanks,

Control-M vs SQL Server Agent

Hi
We have a plan to migrate from SQL Server Agent to Control for job scheduling.
For those who have done this or attempted to it, I would be very grateful if
you could share some of your experience.
I would be interested in:
- Which scripting language did you use for wrapper scripts?
- Did you continue using maintenance plans for backups, dbcc's, re-indixing,
etc.?
- How did you run dts packages from control-M and were you able to report
useful message through control-M?
- Why would you, or would you not, migrate to control-M
Many thanks,
Hi
We are at a start of a 300 SQL Server 2000 migration project to Control-M.
It is the corporate standard, so we don't have much choice.
We will probably use Perl for the wrappers, but VBS might still be used.
Everything will be migrated, but we have a toolset of Perl scripts that does
backups, restores, cold loads etc. This will help a lot.
The DTS stuff, well, it will be moved, but I don't think we will get good
error reporting out of it, unless each DTS package logs what it is doing.
In 60 days, we have to be finished.....
Regards
Mike
"dave222" wrote:

> Hi
> We have a plan to migrate from SQL Server Agent to Control for job scheduling.
> For those who have done this or attempted to it, I would be very grateful if
> you could share some of your experience.
> I would be interested in:
> - Which scripting language did you use for wrapper scripts?
> - Did you continue using maintenance plans for backups, dbcc's, re-indixing,
> etc.?
> - How did you run dts packages from control-M and were you able to report
> useful message through control-M?
> - Why would you, or would you not, migrate to control-M
> Many thanks,

control-m and sql25k

Hi everyone,
Does anyone know if control-m environment is be able to get in touch with
SSIS packages?
Thanks in advance,"Enric" <vtam13@.terra.es.(donotspam)> wrote in message
news:BB5C5E4B-6D49-45F8-AEAA-DF33905FC448@.microsoft.com...
> Hi everyone,
> Does anyone know if control-m environment is be able to get in touch with
> SSIS packages?
> Thanks in advance,
>
Do you mean Control-M on a mainframe or Control-M (ECS) on a UNIX box?
We use both. On the mainframe we use it to kick off a job that talks to the
DBMS. In our case it's Oracle but the principle is the same. On UNIX we use
Control-M (ECS) to kick off a UNIX script which does the equivalent (runs
SQL Plus for instance) to what the mainframe job does in that environment.
I don't know if this answers your question or not.