| Author |
Re: Migrate from Sql Server 2005 to Sql Server 2000
|
|
| Massa Batheli 2006-10-24, 6:28 pm |
|
Dan Guzman wrote:[color=darkred
]
>
> That's the way to go back to SQL 2000. There should be a way to get more
> details about the errors. Are you logging errors in your package?
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
>
> "Massa Batheli" <mngong@gmail.com> wrote in message
> news:1158271663.636547.75900@b28g2000cwb.googlegroups.com...
let me attach the error if do not mind
An OLE DB record is available. Source: "Microsoft SQL Native Client"
Hresult: 0x80040E37 Description: "Invalid object name
'dbo.qs_globals'.".
helpFile=dtsmsg.rll helpContext=0
idofInterfaceWithErr
or={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
Task failed: Transfer SQL Server Objects Task
SSIS package "Package.dtsx" finished: Success.
It seems to have trouble recreating any tables not owned by dbo. when
that is deselected from the list it then has trouble copying any
table...
Thanks again for your time
| |
| Dan Guzman 2006-10-24, 6:28 pm |
| > It seems to have trouble recreating any tables not owned by dbo. when
> that is deselected from the list it then has trouble copying any
> table...
You might try creating SQL 2000 database users for non-dbo SQL 2005 schema
before the transfer. I'm not sure how the Transfer SQL Server Objects Task
handles schema-->owner translation when you copy from SQL 2005 to 2000.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Massa Batheli" <mngong@gmail.com> wrote in message
news:1158320760.263256.231650@h48g2000cwc.googlegroups.com...
>
> Dan Guzman wrote:
>
> let me attach the error if do not mind
>
> An OLE DB record is available. Source: "Microsoft SQL Native Client"
> Hresult: 0x80040E37 Description: "Invalid object name
> 'dbo.qs_globals'.".
> helpFile=dtsmsg.rll helpContext=0
> idofInterfaceWithErr
or={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
> Task failed: Transfer SQL Server Objects Task
> SSIS package "Package.dtsx" finished: Success.
> It seems to have trouble recreating any tables not owned by dbo. when
> that is deselected from the list it then has trouble copying any
> table...
>
>
> Thanks again for your time
>
| |
| Dan Guzman 2006-10-24, 6:28 pm |
| > Are you aware of any other feasible method...
Not really, but it should be reasonably easy to fall back by keeping the
original SQL 2000 database around. Script out the original database foreign
keys and truncate tables. If you make schema changes, apply the scripts to
both SQL 2000 and SQL 2005 database to keep them in sync. To revert back,
copy data back and recreate foreign keys via script.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Massa Batheli" <mngong@gmail.com> wrote in message
news:1158324606.863195.166810@m73g2000cwd.googlegroups.com...
>
> Dan Guzman wrote:
>
> That was quicker than any reply I have ever had (Thanks)
> I will continue to persue that path though we are migrating tomorrow .
> Are you aware of any other feasible method...
>
|
|
|
|