none
SSIS Database Transfer Task failure RRS feed

  • Question

  • Hi,

    The Database Trasnfer Task has failed with the following error......

    failed with the following error: "Invalid object name 'dbo.exampleViewName.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    Does anybody know what this means?

    Thanks,

    Ben


    Mr Shaw... One day I might know a thing or two about SQL Server!

    Wednesday, April 22, 2015 10:14 AM

Answers

All replies

  • This quite clearly indicates that the table/view "exampleViewName" is not locatable, few reasons for you to check:

    • Are you connected to right Server+Database
    • Does it belong to dbo schema or is it something else

    Good Luck! Please Mark This As Answer if it solved your issue. Please Vote This As Helpful if it helps to solve your issue

    Wednesday, April 22, 2015 10:21 AM
  • That means that it cant find the object in the database. Has the table being dropped since the creation of the package?

    Please check if table is still present in db and is under correct schema


    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    ----------------------------
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

    Wednesday, April 22, 2015 10:22 AM
  • Do you have any existing database objects that reference the (now deleted) view?

    See here:

    http://mssqlwiki.com/tag/copy-database-invalid-object-name/
    Wednesday, April 22, 2015 10:24 AM
  • This quite clearly indicates that the table/view "exampleViewName" is not locatable, few reasons for you to check:

    • Are you connected to right Server+Database
    • Does it belong to dbo schema or is it something else

    Good Luck! Please Mark This As Answer if it solved your issue. Please Vote This As Helpful if it helps to solve your issue

    the view is not in the dbo schema.

    I would have thought that the task would create new schemas first and then create objects.


    Mr Shaw... One day I might know a thing or two about SQL Server!

    Wednesday, April 22, 2015 10:30 AM
  • That means that it cant find the object in the database. Has the table being dropped since the creation of the package?

    Please check if table is still present in db and is under correct schema


    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    ----------------------------
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

    No the table has no been dropped.

    I am running the task with the source database online.


    Mr Shaw... One day I might know a thing or two about SQL Server!

    Wednesday, April 22, 2015 10:31 AM
  • Hello everybody....

    I had a look at the script in the view. It is referencing another database which nolonger exists on the server.

    Thankyou for prompting me to think about this.

    I will now look through all the script to see if there are any broken denedencies.

    Oh....Is it possible to to script failed objects using the Transfer Database Task?

    Regards,

    Ben


    Mr Shaw... One day I might know a thing or two about SQL Server!

    Wednesday, April 22, 2015 10:36 AM
  • Mr Shaw - Good to know that.

    No Transfer data task serves different purpose


    Good Luck! Please Mark This As Answer if it solved your issue. Please Vote This As Helpful if it helps to solve your issue

    Wednesday, April 22, 2015 11:06 AM
  • Hello everybody....

    I had a look at the script in the view. It is referencing another database which nolonger exists on the server.

    Thankyou for prompting me to think about this.

    I will now look through all the script to see if there are any broken denedencies.

    Oh....Is it possible to to script failed objects using the Transfer Database Task?

    Regards,

    Ben


    Mr Shaw... One day I might know a thing or two about SQL Server!

    If you have a look at the link I provided it has a script to detect broken dependencies. I haven't tested this myself but it may help.

    Wednesday, April 22, 2015 11:06 AM