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,

Controling Replation agent actions

Hello there
I some questions:
1. Iw'd like to run some store procedures before i'm starging the
replication every day. Dose it enouth to add the task before the replication
task?
2. If the replication faild i would like to make sure that none of the
changes will be made.
3. IF an error occur can i nevegat it to the type of error:
if the error is data error(validation of foreign key) or connection error.
So i can give it order to run 5 minutes afterword?
4. Can i output the errors to outside files in order that other programs
that use sql server (Access) can give a message to the user?
Roy,
adding another step would be fine, or another job which runs sp_start_job
after your code had finished.
Trapping errors is really well catered fro in SQL 2005 but not so easy in
SQL 2000. You'd be better testing your changes in code rather than
attempting your changes eg look for a PK value before trying the FK insert.
If the PK doesn't exist, then logging this to a table and taking appropriate
actions eg making your own error message available to Access.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||1) I would make these procs the first job step of your replication job
2) Double click on the job step, select advanced and have it run a job or
script on failure.
3) This is a little tricky - the error should be in the msrepl_errors table
in the distribution database where the agent is run. You can query it there,
but the error may not be there depending on the error message. What you
would need to do is restart the agent on failure, but this time use the
verbose agent profile. The complete error message will now be in the
msrepl_Errors table. Errors are also logged in text files and dumped in
%WindDir%\system32 and will have an err extension. You can poll for them
using FileSystemWatcher.
4) You might want to poll msrepl_errors as discussed above and write to an
access database. Or you could fire something using the Replication Alert
Agent Failure.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Roy Goldhammer" <roy@.hotmail.com> wrote in message
news:ePub0LyAGHA.2656@.tk2msftngp13.phx.gbl...
> Hello there
> I some questions:
> 1. Iw'd like to run some store procedures before i'm starging the
> replication every day. Dose it enouth to add the task before the
> replication
> task?
> 2. If the replication faild i would like to make sure that none of the
> changes will be made.
> 3. IF an error occur can i nevegat it to the type of error:
> if the error is data error(validation of foreign key) or connection error.
> So i can give it order to run 5 minutes afterword?
> 4. Can i output the errors to outside files in order that other programs
> that use sql server (Access) can give a message to the user?
>
>
|||Whell Hilary
I've made an error in the replication and no MSRepl_Errors table were
created
After i got the error when i run the agent on the enterprise manager i
opened the query anlyser with the distribution database and i counldn't see
the table
When will the table appear?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OYG7KczAGHA.272@.TK2MSFTNGP09.phx.gbl...
> 1) I would make these procs the first job step of your replication job
> 2) Double click on the job step, select advanced and have it run a job or
> script on failure.
> 3) This is a little tricky - the error should be in the msrepl_errors
> table in the distribution database where the agent is run. You can query
> it there, but the error may not be there depending on the error message.
> What you would need to do is restart the agent on failure, but this time
> use the verbose agent profile. The complete error message will now be in
> the msrepl_Errors table. Errors are also logged in text files and dumped
> in %WindDir%\system32 and will have an err extension. You can poll for
> them using FileSystemWatcher.
> 4) You might want to poll msrepl_errors as discussed above and write to an
> access database. Or you could fire something using the Replication Alert
> Agent Failure.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Roy Goldhammer" <roy@.hotmail.com> wrote in message
> news:ePub0LyAGHA.2656@.tk2msftngp13.phx.gbl...
>

context in trigger

Hi All,
I need to know if there is any methode to detect within a trigger, that it
was fired because of merge agent update of the table and not because of the
application's update.
Thanks.
query sessionproperty('replication_agent') to see if its value is 0. If so
a replication agent is making the update, if it is 1, it is another user
process.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Oussama Albairat" <OussamaAlbairat@.discussions.microsoft.com> wrote in
message news:990BF6F4-FF7A-4F76-B560-D9A02261FA3D@.microsoft.com...
> Hi All,
> I need to know if there is any methode to detect within a trigger, that
it
> was fired because of merge agent update of the table and not because of
the
> application's update.
> Thanks.
|||Hi Hilary,
Thank you for the indication. But I noticed that the condition should be
evaluated as in replication triggers : if (
sessionproperty('replication_agent') = 1 and (select trigger_nestlevel()) =
1) the first part alone is not enough to detect that the trigger has been
fired by replication agent.
Thanks.
"Hilary Cotter" wrote:

> query sessionproperty('replication_agent') to see if its value is 0. If so
> a replication agent is making the update, if it is 1, it is another user
> process.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Oussama Albairat" <OussamaAlbairat@.discussions.microsoft.com> wrote in
> message news:990BF6F4-FF7A-4F76-B560-D9A02261FA3D@.microsoft.com...
> it
> the
>
>