Post reply

Stored Procedure Does not exist, what yes it does

  • September 5, 2011 at 10:37 am

    #243324

    I am creating a report in SSRS 2005 and have successfully created my stored procedure and refreshed the database that it resides in. But when I try to enter the name of the stored procedure in the query for the dataset, in the Data tab of the report generator , I get the error:

    "The stored procedure 'sp_DigitalFolderTrends' does not exist'

    I think it might be because the database that I need to make my datasource was not in my "shared data source" list, so would this error be caused by not using a shared datasouce.

  • September 5, 2011 at 11:49 am

    #1377121

    How do you make the connection to the database?

    Are you sure you created the sp in the correct database?

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • September 5, 2011 at 12:31 pm

    #1377139

    Well all the other reports in the directory use one of several shared data source references. Only problem is , I am creating a new report and the database I need to use is not one of the shared data source references. I tried just unchecking "use shared data source reference" and entered a type: Microsoft SQL Server and a connection string: Data Source=VSERVER18;Initial Catalog=DFLT: . Which is the right string. just the server and the database.

    What I need to do is create a shared data source reference of the database I need, Or another option. Just need to connect to the database.

    Thanks for any advice.

  • September 6, 2011 at 5:29 am

    #1377304

    Does the dbo schema own the stored proc?

    Carlton..

  • September 6, 2011 at 6:58 am

    #1377367

    Carlton Leach (9/6/2011)

    Does the dbo schema own the stored proc?

    Carlton..

    I was thinking along the same lines...it might not be owned by dbo:

    select

    schema_name(schema_id) as SchemaName,

    name as ObjectName

    from sys.objects

    where name='sp_DigitalFolderTrends'

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • September 6, 2011 at 8:30 am

    #1377439

    I know that this is a long shot but if the database is case sensitive, then objects’ names (including your procedure’s name) are also case sensitive.

    Adi

    --------------------------------------------------------------
    To know how to ask questions and increase the chances of getting asnwers:
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • September 6, 2011 at 1:50 pm

    #1377666

    Does the SQL Server user used by your Reporting Services instance have EXECUTE permission on the stored proc? (If you're experiencing this problem when working in a local instance of BIDS, do you have EXECUTE permission on the stored proc?) IIRC, SSRS will return the "stored procedure does not exist" error when the user does not have EXECUTE permission on the stored proc. That error message is very misleading under those circumstances, because the stored proc definitely exists on SQL Server but SSRS just can't get to it.

    Jason Wolfkill

  • September 6, 2011 at 2:13 pm

    #1377671

    I have seen that error before on many occasions and it was a permissions issue.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • September 7, 2011 at 2:29 pm

    #1378275

    stupid mistake on my part, its fixed. Was calling be wrong name. I feel dumb.

  • September 7, 2011 at 5:10 pm

    #1378307

    bestep420 (9/7/2011)

    stupid mistake on my part, its fixed. Was calling be wrong name. I feel dumb.

    Been there, done that.

    Welcome to the club! 🙂

Viewing 10 posts - 1 through 9 (of 9 total)

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