• Replies 3 replies
  • Subscribers 336 subscribers
  • Views 79 views
  • Users 0 members are here
Related

Duplicate merge report

Kathleen Smith
$organization

Hi everyone,

 

We use the Duplicate Merge Report fairly heavily, and it’s been reported to me that post-upgrade, the vast majority of merges are listed as scheduled by ‘dbo’ rather than the user who physically scheduled the merges.  Has anyone else noticed this, or can you think of any way to get it back to reporting the user rather than dbo?  I thought I’d try the brain trust here before submitting a ticket… 

 

Cheers,

Kathleen

 

Parents
  • $organization

    Thanks Ken and Wayne! 

     

    Cheers,

    Kathleen

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ken McSwain
    Sent: Wednesday, 8 May 2013 3:28 AM
    To: Kathleen Smith
    Subject: Re: [Tessitura Technical Forum] Duplicate merge report

     

    Hi Kathleen (and Wazza)

    Actually, I think it's a known bug. If you schedule it manually, it gets your userid on it, but if you select from the potential dupe list it shows up as dbo.

    I thought it was fixed in 11.0.4, but it appears not.



    Sent from the iPad


    On 07/05/2013, at 17:34, "Wayne Evans" <bounce-wayneevans6619@tessituranetwork.com> wrote:

    If you are adding merges to be done  overnight, I'd expect the user to be dbo, as thats the username running the job.  
    If you're running the merge now logged on as you, you are running the job, so it should return back as your username.

    We do all scheduled, so I think all ours are dbo.

    Hope this makes sense

    Thanks

    Wayne 

Reply
  • $organization

    Thanks Ken and Wayne! 

     

    Cheers,

    Kathleen

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ken McSwain
    Sent: Wednesday, 8 May 2013 3:28 AM
    To: Kathleen Smith
    Subject: Re: [Tessitura Technical Forum] Duplicate merge report

     

    Hi Kathleen (and Wazza)

    Actually, I think it's a known bug. If you schedule it manually, it gets your userid on it, but if you select from the potential dupe list it shows up as dbo.

    I thought it was fixed in 11.0.4, but it appears not.



    Sent from the iPad


    On 07/05/2013, at 17:34, "Wayne Evans" <bounce-wayneevans6619@tessituranetwork.com> wrote:

    If you are adding merges to be done  overnight, I'd expect the user to be dbo, as thats the username running the job.  
    If you're running the merge now logged on as you, you are running the job, so it should return back as your username.

    We do all scheduled, so I think all ours are dbo.

    Hope this makes sense

    Thanks

    Wayne 

Children
No Data