'table could not be loaded' error in EM

  • I am getting a 'table could not be loaded message' from Eneterprise Manager after a restore. Could someone tell me why this is happening?

    Thanks

  • What's your SQL Version and Service pack?

    Shas3

  • What's your SQL Version and Service pack?

    EDIT - Also where the backup taken ?

    Shas3

  • sql2000 service pack 3

  • backup was taken from production database and restored back to production.

  • quote:


    I am getting a 'table could not be loaded message' from Eneterprise Manager after a restore. Could someone tell me why this is happening?


    did you check db status via QA?

    Also, when do you get this error?

    I think I have this (or a similar) error message seen when setting EM view to taskpad and then trying to get to Table Info tab. However, it went away after a while. All the time the db was alive and well.

    Cheers,

    Frank

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • The db is fully operational it is just that I am getting this error when trying to design a table, add a table, magange a trigger etc....

    I get a message : table 'x' could not be loaded followed by invalid column name 'x'

    invalid column name 'y'

    invalid column name 'z'

    Thank you for the help

  • Yes you are right a5, when you see the tables from the EM, it may not show the tables in the Task pad view if the table does not have an index. This behavior is corrected in SP2

    Shas3

  • quote:


    Yes you are right a5, when you see the tables from the EM, it may not show the tables in the Task pad view if the table does not have an index. This behavior is corrected in SP2


    Aah, that's was the reason it went away

    Good to know for the future, thanks!

    Cheers,

    Frank

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • Thank you both...

    error message is titled

    ms sql-dmo (odbc sqlstate: 42S22)

  • MS says they resolved this in SP1? Are you still getting the error

    Shas3

  • Yes I am still getting the error. I am running SP3.

  • Try to the following if you can

    1) BCP out the X table data

    2) Script the table X

    3) Drop the table X

    4) Do some objects creation and manipulate your trigger

    5) Create table X from the script and BCP in

    Shas3

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply