November 3, 2009 at 9:03 am
Yes, another Copy DB question. But I'll try to make mine a little more specific:
Copy DB Wizard fails during execution (not using the Attach/Detach method...need to keep the DB online). The only entries in the log file are these, but they don't seem to explain WHY the Copy wizard is failing:
- SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
- SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
- SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
Here's the additional useful info:
- Auto Close property of source DB is set to FALSE
- Source and Destination are SQL 2005 9.00.4035.00 (i.e. SP3)
- I am a member of the sysadmin role on both servers
What am I doing wrong? The only other thing that comes to mind is that SINCE the wizard is creating and executing this as an SSIS package, maybe I MUST use a proxy account that's a member of SysAdmin?
November 3, 2009 at 9:21 am
Two updates:
1. Found the actual error from the first attempt:
Description: ERROR : errorCode=-1073451000 description=The package contains two objects with the duplicate name of "output column "ErrorCode" (199)" and "output column "ErrorCode" (14)".
2. Tried again, but this time used a proxy account with SysAdmin rights (i.e. my own domain credentials). Got this error:
Code: 0xC001403D Source: Description: The log provider type "DTS.LogProviderEventLog.1" specified for log provider "{BEA633DB-9705-4540-9206-00A425D823BD}" is not recognized as a valid log provider type. This error occurs when an attempt is made to create a log provider for unknown log provider type. Verify the spelling in the log provider type name.
At this point, I think the error from the first attempt makes a little more sense. I'll pursue that one and see what happens.
November 3, 2009 at 2:10 pm
Just following-up. Turns out the SSIS package created by the Copy DB wizard didn't like the fact that one of my tables had a column named, "ErrorCode" (the table in question is a destination table I creatd to capture failed SSIS inserts...and the redirected error row contains a field named, "ErrorCode"). I renamed the column to, "SSISErrorCode" and the Copy DB Wizard's SSIS package worked fine.
:doze:Not sure what to think...seems like the Copy DB Wizard shouldn't really care about the column names in the source database, as long as they are valid...but whatever. I guess it reserves the right to be the only one that can create a package with an output named, "ErrorCode."
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply