I have created a DTS Package on a new SQL 2000 SP2 Server running Win2K
Advanced. I am trying to import an 11GB user DB from a SQL 7 NT4 Server,
copying all DB objects, overwriting any existing DB objects in the
destination server. I scheduled it to run when there were no users in
either DB Server. It failed after running for 1:24, with the following
error in the SQL Server log and the Win2K Application Event Log:
**************
SQL Server Scheduled Job 'XXX Data' (0xEE308DDE4E12E5469B073F751E6C737F)
- Status: Failed - Invoked on: 2003-12-31 03:01:00 - Message: The job
failed. The Job was invoked by Schedule 2 (Sched2). The last step to
run was step 1 (XXX Data).
**************
Not very informative. The target DB does already exist in the
destination server. Should I drop it? Any other recommendations?
TIA,
JCWhat does the details of the step in the Job History show? In any case why
go through all that trouble. If your copying everything a simple backup and
restore or detach and attach would be quicker and less prone to failure.
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=274463 Copy DB
Wizard issues
Andrew J. Kelly
SQL Server MVP
"JimC" <JC@.spamhole.com> wrote in message
news:3FF35323.7030505@.spamhole.com...
> I have created a DTS Package on a new SQL 2000 SP2 Server running Win2K
> Advanced. I am trying to import an 11GB user DB from a SQL 7 NT4 Server,
> copying all DB objects, overwriting any existing DB objects in the
> destination server. I scheduled it to run when there were no users in
> either DB Server. It failed after running for 1:24, with the following
> error in the SQL Server log and the Win2K Application Event Log:
> **************
> SQL Server Scheduled Job 'XXX Data' (0xEE308DDE4E12E5469B073F751E6C737F)
> - Status: Failed - Invoked on: 2003-12-31 03:01:00 - Message: The job
> failed. The Job was invoked by Schedule 2 (Sched2). The last step to
> run was step 1 (XXX Data).
> **************
> Not very informative. The target DB does already exist in the
> destination server. Should I drop it? Any other recommendations?
> TIA,
> JC
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment