Hello,
I am trying to use the copy database funtion from sql2000 to sql2005. It
fails miserably and logs only says:
step 0: The job failed. The Job was invoked by User domain\user. The last
step to run was step 1 (CDW_DBSERVERNAME_USERMACHINE_1_Step).
step 1: Executed as user: domain\user. The package execution failed. The
step failed.
There is no destination db already existing, the feature drop any database
on the destination server is activated, it fails at Execute SQL Server Agent
Job.
Although the database is created there is no tables created.
The user in the source and destination server is the same for the sql
service and the agent.
I am a bit lost. Is ity possible to do that between sql2k and sql2k5?
Thanks for the help
WilfridIf you are copying the whole db why not just restore from a full backup of
the 2000 db on 2005?
--
Andrew J. Kelly SQL MVP
"Wilfrid" <grille11@.yahoo.com> wrote in message
news:4399b19d$0$22164$afc38c87@.news.easynet.fr...
> Hello,
> I am trying to use the copy database funtion from sql2000 to sql2005. It
> fails miserably and logs only says:
> step 0: The job failed. The Job was invoked by User domain\user. The
> last step to run was step 1 (CDW_DBSERVERNAME_USERMACHINE_1_Step).
> step 1: Executed as user: domain\user. The package execution failed. The
> step failed.
> There is no destination db already existing, the feature drop any database
> on the destination server is activated, it fails at Execute SQL Server
> Agent Job.
> Although the database is created there is no tables created.
> The user in the source and destination server is the same for the sql
> service and the agent.
> I am a bit lost. Is ity possible to do that between sql2k and sql2k5?
> Thanks for the help
> Wilfrid
>|||The process of dumping a db from one server and then restore it to another server takes longer than just using a feature
available form sql2k5.
I was using, with sql2k, the exporting objects functionnality from one server to another but this feature is not
available anymore with sql 2k5 and I believe it has been replaced with the copy db.
Andrew J. Kelly wrote:
> If you are copying the whole db why not just restore from a full backup of
> the 2000 db on 2005?
>|||The copy db functionality was available in 200 as well and is not new. But
it is usually not faster or cleaner than a backup and restore. You should
already be doing regular backups so all you have to do is issue the restore.
You don't even have to copy the file first. As long as the folder is
accessible from the other server you can restore directly from there.
--
Andrew J. Kelly SQL MVP
"grille11" <grille11@.yahoo.com> wrote in message
news:439b429e$0$22164$afc38c87@.news.easynet.fr...
> The process of dumping a db from one server and then restore it to another
> server takes longer than just using a feature available form sql2k5.
> I was using, with sql2k, the exporting objects functionnality from one
> server to another but this feature is not available anymore with sql 2k5
> and I believe it has been replaced with the copy db.
>
> Andrew J. Kelly wrote:
>> If you are copying the whole db why not just restore from a full backup
>> of the 2000 db on 2005?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment