[Transfer SQL Server Objects Task] Error: Table does not exist at the source.

Hello,

I am running a package that used to transfers data from one SQL2005 to another SQL2005. There are multiple schemas associated with the database. Until recently, this pacakage would work. Now I am getting the following error for all the tables not owned by dbo:

Any help on this would be appreciated.

Thanks, sck10

[Transfer SQL Server Objects Task] Error: Table "tblAudiocast" does not exist at the source.

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600

May be it;s a direct error that in the source "tblAudiocast" table may not be exisiting or renamed!!!

Or check the connection strings if it's pointing to the correct data base!!

Dev

|||

Thanks Dev, but all the tables exist. We copy the schema from the production database to the local database, so they are duplicates. And it works for tables that belong to dbo only, but fails for all other tables.

sck10

|||

This thread describes the same problem - it's a known bug. It may have been fixed in SP2, but I'm not positive.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=207812&SiteID=1

|||

Thanks jwelch,

My SSIS package was working until recently.

sck10

sql

[Transfer SQL Server Objects Task] Error: Table does not exist at the source.

Hello,

I am running a package that used to transfers data from one SQL2005 to another SQL2005. There are multiple schemas associated with the database. Until recently, this pacakage would work. Now I am getting the following error for all the tables not owned by dbo:

Any help on this would be appreciated.

Thanks, sck10

[Transfer SQL Server Objects Task] Error: Table "tblAudiocast" does not exist at the source.

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600

May be it;s a direct error that in the source "tblAudiocast" table may not be exisiting or renamed!!!

Or check the connection strings if it's pointing to the correct data base!!

Dev

|||

Thanks Dev, but all the tables exist. We copy the schema from the production database to the local database, so they are duplicates. And it works for tables that belong to dbo only, but fails for all other tables.

sck10

|||

This thread describes the same problem - it's a known bug. It may have been fixed in SP2, but I'm not positive.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=207812&SiteID=1

|||

Thanks jwelch,

My SSIS package was working until recently.

sck10

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the source

Does anyone know what could be causing the error on Transfer SQL Server Objects Task? I tried to develope a SSIS project in the Business Intelligence studio to transfer table between databases on the same server. However, I have been getting the following error:

[Transfer SQL Server Objects Task] Error: Table "XXXXXX" does not exist at the source.

Is there a setting that I need to change to make this work? Thank you for your help.

Is the table you've specified to move on the task in the source database?|||

Yes. It is in there. I can see it in the selection list after I select the database. Thanks.

And Transfer SQL Server Objecdts Task is the only task in that SSIS package.

|||I think your problem is related to the schema of the table you are trying to copy.

I created table "testtable" in testdb1. The schema was "dbo". I could transfer this table to another database named testdb2 in the same server using Transfer SQL Server Objects Task.

Then, I changed the schema of "testtable" to "guest". When I executed the same task, I got the error message "[Transfer SQL Server Objects Task] Error: Table "testtable" does not exist at the source. "|||

Thanks for your response. Where di you create the "Transfer SQL Server Objects Task"? Is it under control flow or data flow? When I had the error to only task I had was the "Transfer SQL SErver Obejcts Task" under Control Flow.

Thanks.

|||Transfer SQL Server Objects is a Control Flow task. I had my task in the control flow tab and the task I have explained above was the only task I had in the package.|||I had the exact issue when I transfer the data (both table and xml schema) from my dev. box to the production server. It seemed to me that this particular control task recognizes only the dbo schema. Is this bug fixed in SP1?|||No. We are looking to fix this issue in one of the future releases.|||I am trying to figure out exactly what the issue is here -- can we not copy tables from one database to another at all at this time? I had both tables as dbo schemas, and I had a different error, this time about the destination not being available. I set the schema owner of the tables to be the same as the authenticated user, and then I received the error that it does not exist at the source.

At this time (10/2006), is there any way to copy tables from one server to another via SSIS? I would think this basic of a task would be the first to work on a newer DTS... ?

Thanks in advance

-Chris Rasmussen|||

I am hoping someone will answer the last question. I cannot beleive you would release a product with such a simple task not working. As a workaround, I suppose I can create an SMO task to handle this, but that is more development time than I had expected to use. Please fix this with your NEXT release, not an undetermined FUTURE release. This type of missing functionality is hard to point at and convince anyone in the position of making decisions to migrate to 2005. Come on guys and gals.

Your frustrated supporter...

|||

Hi Cliff!

I'd like to share my frustration with Transfer SQL Server Object Task. I am trying to do something very simple - transfer 3 tables with primary/foreign keys, referential ingegrity and some data and spent hours of fruitless tweaking of the task. If someone offers a very simple step by step process on how to configure the "Transfer SQL Server Object task" to do that, I would be very grateful.

|||Are you planning on fixing this in SP2?|||Hi

I'd like to add my vote for this feature request. Can someone from the dev team tell if the decision of fixing this has already been taken somehow ?

Any insight will be most welcome, and will help us pick the right solution.

Thibaut Barrère|||

Hi,

I am also having problems with the "Transfer SQL Server Objects" task. It simply does not work.

The editor interface is sweet, however, and looks very promising. My issue is that I cannot debug this task. I cannot see the code that is generated by the task, and logging does not reveal what I want: the SQL code or whatever code is generated by the task. I want to see the actual table name syntax contained in the resultant command sent over, with the assumption that there is something wrong there.

The documentation is very clear, promising effective results. The reality is different, however. This is simply a management issue. The product was released too early, and the testing regimen must have been inadequate or mismatched with the document.

I have the Evaluation Version of Enterprise. The SMO connectors all test properly, and there is no other problem. The wizard works fine from SSMS, and when I save the output from the wizard to a package, the package does not use the "Transfer SQL Server Objects" task.

So, guys, what we have here is a defect.

This is very annoying, and I will write a letter to Bill Gates requesting immediate attention to this issue.

|||The fix is not released yet.

[Transfer SQL Server Objects Task] Error: Table "XXXXXXX" does not exist at the source

Does anyone know what could be causing the error on Transfer SQL Server Objects Task? I tried to develope a SSIS project in the Business Intelligence studio to transfer table between databases on the same server. However, I have been getting the following error:

[Transfer SQL Server Objects Task] Error: Table "XXXXXX" does not exist at the source.

Is there a setting that I need to change to make this work? Thank you for your help.

Is the table you've specified to move on the task in the source database?|||

Yes. It is in there. I can see it in the selection list after I select the database. Thanks.

And Transfer SQL Server Objecdts Task is the only task in that SSIS package.

|||I think your problem is related to the schema of the table you are trying to copy.

I created table "testtable" in testdb1. The schema was "dbo". I could transfer this table to another database named testdb2 in the same server using Transfer SQL Server Objects Task.

Then, I changed the schema of "testtable" to "guest". When I executed the same task, I got the error message "[Transfer SQL Server Objects Task] Error: Table "testtable" does not exist at the source. "|||

Thanks for your response. Where di you create the "Transfer SQL Server Objects Task"? Is it under control flow or data flow? When I had the error to only task I had was the "Transfer SQL SErver Obejcts Task" under Control Flow.

Thanks.

|||Transfer SQL Server Objects is a Control Flow task. I had my task in the control flow tab and the task I have explained above was the only task I had in the package.|||I had the exact issue when I transfer the data (both table and xml schema) from my dev. box to the production server. It seemed to me that this particular control task recognizes only the dbo schema. Is this bug fixed in SP1?|||No. We are looking to fix this issue in one of the future releases.|||I am trying to figure out exactly what the issue is here -- can we not copy tables from one database to another at all at this time? I had both tables as dbo schemas, and I had a different error, this time about the destination not being available. I set the schema owner of the tables to be the same as the authenticated user, and then I received the error that it does not exist at the source.

At this time (10/2006), is there any way to copy tables from one server to another via SSIS? I would think this basic of a task would be the first to work on a newer DTS... ?

Thanks in advance

-Chris Rasmussen
|||

I am hoping someone will answer the last question. I cannot beleive you would release a product with such a simple task not working. As a workaround, I suppose I can create an SMO task to handle this, but that is more development time than I had expected to use. Please fix this with your NEXT release, not an undetermined FUTURE release. This type of missing functionality is hard to point at and convince anyone in the position of making decisions to migrate to 2005. Come on guys and gals.

Your frustrated supporter...

|||

Hi Cliff!

I'd like to share my frustration with Transfer SQL Server Object Task. I am trying to do something very simple - transfer 3 tables with primary/foreign keys, referential ingegrity and some data and spent hours of fruitless tweaking of the task. If someone offers a very simple step by step process on how to configure the "Transfer SQL Server Object task" to do that, I would be very grateful.

|||Are you planning on fixing this in SP2?|||Hi

I'd like to add my vote for this feature request. Can someone from the dev team tell if the decision of fixing this has already been taken somehow ?

Any insight will be most welcome, and will help us pick the right solution.

Thibaut Barrère

|||

Hi,

I am also having problems with the "Transfer SQL Server Objects" task. It simply does not work.

The editor interface is sweet, however, and looks very promising. My issue is that I cannot debug this task. I cannot see the code that is generated by the task, and logging does not reveal what I want: the SQL code or whatever code is generated by the task. I want to see the actual table name syntax contained in the resultant command sent over, with the assumption that there is something wrong there.

The documentation is very clear, promising effective results. The reality is different, however. This is simply a management issue. The product was released too early, and the testing regimen must have been inadequate or mismatched with the document.

I have the Evaluation Version of Enterprise. The SMO connectors all test properly, and there is no other problem. The wizard works fine from SSMS, and when I save the output from the wizard to a package, the package does not use the "Transfer SQL Server Objects" task.

So, guys, what we have here is a defect.

This is very annoying, and I will write a letter to Bill Gates requesting immediate attention to this issue.

|||The fix is not released yet.

[SBS2003 Premium R2] Reporting services problem

Hi!
When I try configure report data source to connect to database on another
SQL Server 200 i receive message:
The feature: "Remote access to report data sources and/or the report server
database" is not supported in this edition of Reporting Services.
What can I do with thiss message?
Please help me
Best regards
AdamOn Jun 29, 1:57 am, "Adam Kobylinski" <akobylin@.NO_SPAM.op.pl> wrote:
> Hi!
> When I try configure report data source to connect to database on another
> SQL Server 200 i receive message:
> The feature: "Remote access to report data sources and/or the report server
> database" is not supported in this edition of Reporting Services.
> What can I do with thiss message?
> Please help me
> Best regards
> Adam
If you are running SQL Server 2005 Express Edition (w/Advanced
Services), this is one of the limitations. Otherwise, you will want to
open the local SQL Server Surface Area Configuration tool and select
Surface Area Configuration for Services and Connections -> View by
Instance -> MSSQLSERVER (or the local instance name) -> Database
Engine -> Remote Connections and make sure that it is set to: Local
and remote connections. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||User "EMartinez" <emartinez.pr1@.gmail.com>
> On Jun 29, 1:57 am, "Adam Kobylinski" <akobylin@.NO_SPAM.op.pl> wrote:
>> Hi!
>> When I try configure report data source to connect to database on another
>> SQL Server 200 i receive message:
>> The feature: "Remote access to report data sources and/or the report
>> server
>> database" is not supported in this edition of Reporting Services.
>> What can I do with thiss message?
>> Please help me
>> Best regards
>> Adam
>
> If you are running SQL Server 2005 Express Edition (w/Advanced
> Services), this is one of the limitations. Otherwise, you will want to
> open the local SQL Server Surface Area Configuration tool and select
> Surface Area Configuration for Services and Connections -> View by
> Instance -> MSSQLSERVER (or the local instance name) -> Database
> Engine -> Remote Connections and make sure that it is set to: Local
> and remote connections. Hope this helps.
>
Unfortunately it doesn't work, i already have remote connections selected,
SQL server 2000 on other computer is Standard Edition and i can connect
remotely from other applications.
Have you any idea?
Regards
Adam

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

trying to install sql server2005 on a windows 2003 server box.

getting msg below at the sql server . i looked at other posts on trying to uninstall SQL Native Access Client and norton antivirus. i could never find the snac on the add - remove programs and this server does not have a virus protection program yet.

here's the history of the installs on the server:

wanted to test a 2005 upgrade so:

1) installed sql server 2000 then sp4 then restored some databases to it - all OK

2) tried to upgrade to sql 2005 but ran into problems and left it at that.

had a disk drive crash on the d drive so lost the installs but not the operating system

when the drive was replaced, left alone for a while

then wanted to test a straight 2005 install

1) removed the broken 2005 attempt

2) removed the 2000

3) installed 2005 and got the error on the subject line:

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

i've gone through as many of the forums that i can and have tried several things - like uninstalling 2005 and installing pieces and parts but but nothing seems to work.

Thanks!

Dan <><

It sounds like the SNAC version you have might be corrupt or incompatible.

Go to Add or Remove Programs and find the listing for "Microsoft SQL Native Client". Remove this component.

Then try the install again.

Michelle

|||

Thank you so much for replying. last attempt was to install just the sql server commonent - no others like analysis services or integration services.

i looked at the add / remove programs both before, during and after the sql server database services failed attempt and the add/remove has never shown a program called MS sql native access client (SNAC).

when i start the install, the installing prerequisites window shows the two components that will be installed: snac and the sql server 2005 setup support files. the snac goes to a green arrow almost immediately while the 2005 setup files takes a few seconds. i dont know if that helps or not.

the add remove programs just has:

microsoft .net framwork 2.0|||

It definatel looks like the problems is the "Microsoft SQL Server Native Client" layer. At this point your machine thinks that it is already installed but the install is broken.

Follow the directions in the following article to clean up the machine and then try again.

http://support.microsoft.com/kb/909967

Michelle

|||

uninstall manually - did the following (shows issues with some of the directions)

it said to delete the local security groups. but i never could figure out how to do. the article it mensions didnt (at least to me) show how to delete. so i just went on|||

i went out to the website and downloaded the .msi file for snac. it was slightly different from the .msi that came on the DVD (3511k vs 3516k).

the dvd version when i clicked on the msi file just returned me back to windows explorer.

the snac from microsoft's website executed and finally installed the snac.

the install worked perfectly after that.

thanks for your help

|||

Actually that was a good work around as downloading a newer version would have forced the install to run again where as in the previous case it was failing quickly becuase it thought it was laready installed.

Glad you got you machine back.

Michelle

|||

Hi,

I've been handling SQL Server upgrades for many years. The most dangerous path for an upgrade is to directly upgrade 2000 to 2005 (or 7.0 to 2000). That's because you create the risk of destroying the databases on the existing server and causing data loss.

The best approach embraces the fact that we typically upgrade a windows server when the mfg warranty on the hardware has expired. So, you have a new box and windows server. If you don't, the store the backups on another resource (disk, tape, flash drive, etc...) and copy from or restore from that resource. Rebuild the Windows server or uninstall SQL Server 2000. (I would have fresh windows to insure the best chance of success.)

Install SQL 2005 & configure on the new W03 SP1 server. migrate the users. (this worked easily with 2K but MS has hosed that functionality in 2005 from what I can see; you must use a script they provided that is flaky. You will need to manually create the users it fails to migrate.) Backup the dbs on 2K, shut down 2K on the old machine and restore the dbs to 2005. associate the users with the logins.

Now you have a fullly upgraded database server and your databases are unhosed. This may not be elegant but it guarantees the MS upgrade process won't destroy your databases or bring down your business for days.

If you have a completely hosed system, then rebuild the system (and the drives) and follow the steps above to a successful conclusion.

z.

[DTS.Pipeline] Warning: The output column "Column 5" (1038) on output "Flat File

[DTS.Pipeline] Warning: The output column "Column 5" (1038) on output "Flat File Source Output" (2) and component "Flat File Source" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.

what the heck does this mean?

More or less what it says - you have a column that is not used by downstream component.

So the data flow issues a warning that it might be better to just remove this column to save buffer space. Of course it is just optimization warning and can be ignored, but if you want maximum performance do pay attention to such warnings.