none
SSRS report builder - cannot see tables RRS feed

  • Question

  • Fellow SSRSers

    We are using SQL 2016 report builder.

    We are buidling a data source, it works perfectly. The sql login and password are fine that the sql login as dbo owner to the database we want to report on (that db is owned by our reporting team). Testing connection is fine.

    When we try to use the data source, we do not see any tables to pick from to build the query. All we see are a few system tables of  names I have never seen - I think that are starting with the letters sf.

    What are we missing.

    thanks

    MG

    Tuesday, January 29, 2019 4:09 PM

Answers

  • Hi Klaus,

    thanks for the info. Nope, the rights were DBO. We may change it to down the road.

    The issue was the connection string. They developer left out a semicolon after the data source entry. Because of this, it appears that it did not use the Initial catalog entry because of this. But it used the default DB named tied to the login (which was master) and they did not have permission to read master.

    Developers added the semicolon and all is fine.

    • Marked as answer by mg101 Tuesday, January 29, 2019 4:38 PM
    • Unmarked as answer by mg101 Wednesday, January 30, 2019 4:39 PM
    • Edited by mg101 Wednesday, January 30, 2019 4:43 PM reworded cause
    • Marked as answer by mg101 Wednesday, January 30, 2019 4:43 PM
    Tuesday, January 29, 2019 4:38 PM

All replies

  • hi 

    sounds like you have not the Rights to your datasource. 

    if you have SQL Management Studio (free) you can test this 

    otherwise check that your user has at least read Rights on the Database.

    the most databases has a Security Role "Data-Reader" this should by fine for you.

    klaus 

    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue


    Klaus

    Tuesday, January 29, 2019 4:17 PM
  • Hi Klaus,

    thanks for the info. Nope, the rights were DBO. We may change it to down the road.

    The issue was the connection string. They developer left out a semicolon after the data source entry. Because of this, it appears that it did not use the Initial catalog entry because of this. But it used the default DB named tied to the login (which was master) and they did not have permission to read master.

    Developers added the semicolon and all is fine.

    • Marked as answer by mg101 Tuesday, January 29, 2019 4:38 PM
    • Unmarked as answer by mg101 Wednesday, January 30, 2019 4:39 PM
    • Edited by mg101 Wednesday, January 30, 2019 4:43 PM reworded cause
    • Marked as answer by mg101 Wednesday, January 30, 2019 4:43 PM
    Tuesday, January 29, 2019 4:38 PM