Azure extended table giving error [ODBC Driver 17 for SQL Server][SQL Server]Invalid object name

MichaelWorkingDowntown 21 Reputation points
2023-01-06T16:39:37.663+00:00

I've already made about ten extended tables in Azure. But this last one is giving me an error saying the object doesn't exist. I am assuming the database in the on premise database. It does exist it's an old database the other tables are being spotted fine and spelling is correct.

Any ideas for error?

Azure SQL Database
{count} votes

1 answer

Sort by: Most helpful
  1. ShaktiSingh-MSFT 16,171 Reputation points
    2023-01-09T04:59:12.953+00:00

    Hi @MichaelWorkingDowntown ,

    Welcome to Microsoft Q&A forum and thanks for using Azure services.

    As I understand from the error [ODBC Driver 17 for SQL Server][SQL Server]Invalid object name, it is received when table is fetched from On Premise Database.
    Please correct me if my understanding is wrong.

    Invalid Object Name could be caused by following reasons which you could look into:

    1). Please make sure the table exists in the database.
    Try to query it to ensure that it exists and fetches data.

    2). Check you are using correct schema to get table.

    3). Check the permissions on the database.

    4). Make sure the connection string is the "right" database. If the user connects to master, for example, instead of the database, you'd get that kind of error.

    5). If the table is in an odd schema, like tlfuser.Tablename instead of dbo.Tablename, you would get the same object not found error.

    Refer to similar error thread which might be useful: sql-server-odbc-errorinvalid-object-name-but-when-i-add-in-sql-query-mydb-dbo

    Hope this helps. Please share your inputs if your issue is solved by using above mentioned checks.
    If not, please share more details about the problem so that we can further assist you. Thanks!

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.