Import data from SQL Server

Hi,
I imported database OldData from SQL Server 6.5 to NewData in SQL Server
2000, and the database can be imported. However, there's no Index in any
table in the NewData.
Would anyone tell me how to fix this problem?
Thanks.
Jason
Hi,
How did you moved the database from SQL 6.5 to SQL 2000? . If you use
"upgrade Wizard" that will automatically copy all objects from SQL 6.5 to
SQL 2000.
If you use DTS or BCP then only the table and data will be transferred to
SQL 2000. You may need to create all the other objects manually.
Thanks
Hari
MCDBA
"Jason" <JASON88@.seed.net.tw> wrote in message
news:c6a41m$oo2$1@.news.seed.net.tw...
> Hi,
> I imported database OldData from SQL Server 6.5 to NewData in SQL Server
> 2000, and the database can be imported. However, there's no Index in any
> table in the NewData.
> Would anyone tell me how to fix this problem?
> Thanks.
> Jason
>
|||Thanks Hari.
I used the upgrade wizard tried to upgrade from 6.5 to 2000, but it show an
error message with SQL-DMO, and the 6.5 has to migrate to 7.0 first.
Is there anyway to upgrade from 6.5 to 2000 without upgrading to 7.0 first?
Thanks for help.
Jason
"Hari" <hari_prasad_k@.hotmail.com> bl
news:OQ93AfOKEHA.2776@.TK2MSFTNGP12.phx.gbl g...[vbcol=seagreen]
> Hi,
> How did you moved the database from SQL 6.5 to SQL 2000? . If you use
> "upgrade Wizard" that will automatically copy all objects from SQL 6.5 to
> SQL 2000.
> If you use DTS or BCP then only the table and data will be transferred to
> SQL 2000. You may need to create all the other objects manually.
> Thanks
> Hari
> MCDBA
>
> "Jason" <JASON88@.seed.net.tw> wrote in message
> news:c6a41m$oo2$1@.news.seed.net.tw...
any
>
|||Hi Jason,
Using the SQL Server Upgrade wizard you can upgrade directly from SQL 6.5 to
SQL 2000. The steps are detailed below:-
1. Ensure that SQL 6.5 is running and all the databases are up (Run DBCC and
check the databaseconsistency)
2. Update the SQL 6.5 service pack to latest , probably sp5a
3. Install SQL 2000 and Sp3a for sql 2000
4. In SQL 2000 program groups there will be upgrade wizard, it will
automatically sence SQL 6.5 and upgrade
the sql 6.5 databases to SQL 2000
5. This upgrade wizrd leave the SQL 6.5 databases safe
6. There will be switch option which can be used to switch between sql 2000
and SQL 6.5
Look into SQL 2000 books online, this has got the detailed steps to perfoerm
upgrade between SQL 6.5 to SQL 2000 with
a. all the prerequisites before upgrade
b. Upgrade steps
c. After Upgrade
(Do not use DTS / BCP... This will take long time)
Thanks
Hari
MCDBA
"Jason" <JASON88@.seed.net.tw> wrote in message
news:c6alu7$qt$1@.news.seed.net.tw...
> Thanks Hari.
> I used the upgrade wizard tried to upgrade from 6.5 to 2000, but it show
an
> error message with SQL-DMO, and the 6.5 has to migrate to 7.0 first.
> Is there anyway to upgrade from 6.5 to 2000 without upgrading to 7.0
first?[vbcol=seagreen]
> Thanks for help.
> Jason
> "Hari" <hari_prasad_k@.hotmail.com> bl
> news:OQ93AfOKEHA.2776@.TK2MSFTNGP12.phx.gbl g...
to[vbcol=seagreen]
to[vbcol=seagreen]
Server
> any
>

Import and Export Wizard throws errors when theres alot of tables

I’m trying to copy data from production to my local machine using the SQL Server 2005 import and export wizard. It works fine if I select a small number of tables but throws errors

When there’s a lot of tables. Have you ever experienced problems using it? Is there a better way to transfer the data?

the data source is SQL Server 2000 and the target is 2005. I have the optimize for many tables and transaction options selected

Here’s the errors I get

Execute the transfer with the TransferProvider. (Error)

Messages

· ERROR : errorCode=-1073451000 description=The package contains two objects with the duplicate name of "output column "ErrorCode" (49)" and "output column "ErrorCode" (14)".
helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

· ERROR : errorCode=-1073451000 description=The package contains two objects with the duplicate name of "output column "ErrorCode" (31)" and "input column "ErrorCode" (52)".
helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

· ERROR : errorCode=-1073451000 description=The package contains two objects with the duplicate name of "output column "ErrorCode" (49)" and "output column "ErrorCode" (14)".
helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

· ERROR : errorCode=-1073451000 description=The package contains two objects with the duplicate name of "output column "ErrorCode" (31)" and "input column "ErrorCode" (52)".
helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

· ERROR : errorCode=-1073451000 description=The package contains two objects with the duplicate name of "output column "ErrorCode" (49)" and "output column "ErrorCode" (14)".
helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

· ERROR : errorCode=-1073451000 description=The package contains two objects with the duplicate name of "output column "ErrorCode" (31)" and "input column "ErrorCode" (52)".
helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

· ERROR : errorCode=-1073451000 description=The package contains two objects with the duplicate name of "output column "ErrorCode" (49)" and "output column "ErrorCode" (14)".
helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC} (Microsoft.SqlServer.DtsTransferProvider)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Umm, do you have existing tables that have a column named, ErrorCode?|||very possible..if so what am i supposed to do to fix the problem ?|||Rename the columns in the tables... Really, not many options to do here.

I have created a Connect bug in relation to this:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=252471

You should go there and vote, with comments, to help give more weight to the bug. Also "validate" it.

Thanks,
Phil|||

Thx, Didn;t see the siginficance of the fact that the column was called ErrorCode Right awy. I've been trying to use Import and Export to load data from production 2000 to local 2005 for several days now and I'm pretty burnt out. The vote does not seem enabled at the moment I'll look at it again tomorrow

|||

Mike C wrote:

Thx, Didn;t see the siginficance of the fact that the column was called ErrorCode Right awy. I've been trying to use Import and Export to load data from production 2000 to local 2005 for several days now and I'm pretty burnt out. The vote does not seem enabled at the moment I'll look at it again tomorrow

You have to sign into Connect before you can vote.