Command(s) completed successfully. only output set parseonly NOT checked

  • Hello,

    I have been trying to solve this for hours. I know it's very likely something really basic but...

    When I run a built in stored procedure, for example sp_helppublication, in SSMS, I just see this:

    Command(s) completed successfully.

    No output. I have checked so many settings. I think I have looked everywhere in the settings for SSMS but maybe not. I definitely don't have the set parseonly checked.

    Could someone please help?

    Thanks in advance.

  • sp_helppublication will return information on all publications that are owned by the user executing this procedure.

    Do you own the publications you're trying to get information on?

  • I am on the Publication Access List (PAL). Thank you for reminding me to check it. I am logged in with a windows user ID with system administrator access. I have never run up against a situation where I didn't have full rights to access anything I wanted.

    Thanks for your reply. Is there anything else I should check?

  • The only thing I'd recommend is what I would do.. find someone else that CAN get information about the publication and see what the differences are between my account and theirs.

  • Ok thank you. I tried connecting as sa and still no luck. I have been trouble finding who the owner of the publications is as it doesn't display in properties. I know I created one today with my own windows ID but the others were created probably by sa (I wasn't around). Do you know where I find who the owner of each publication is? I have tried googling but my keywords - find owner of replication publisher - are bringing everything back about replication except that.

    Thanks again.

  • I always thought that the Agent Job owner was the owner of the distribution. There's the agent security agent but I'm not sure that's the owner.

  • Thanks Erin. I created my newest publication with my windows account and I think I remember reading that replication should be set up with a SQL login. But, the rest of the publications were not created with a windows login. I will post again when I get this figured out but you were absolutely crucial in pointing me in this direction. Thanks!

  • I neglected to mention that all our replications are set up with a SQL Server login. I think you may be on to something there...

Viewing 8 posts - 1 through 7 (of 7 total)

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