Don't worry about having it run in an automated way. The point is just
to have something around that people can run on a production database
(generally after testing it on a staging database that is a clone of
the production database) that will do the data move needed.
In other words, they are to be used as part of a semi-manual upgrade
process. For many of these things I'm not sure that we would want it
to be totally automated (for the same reason it's best to run it on a
staging database first before moving to the production database).
Because people may customize things or have a different revision than
they think they do, or whatever, this becomes pretty important.
-David
On Jun 29, 2008, at 9:05 AM, Adrian Crum wrote:
I need to create a service that runs one time to move records from a
deprecated entity to its replacement.
I know I can schedule a job to run only once, but what do I do with
the deprecated entity? Do I delete the records in it, so the copying
isn't performed again by accident?
-Adrian
