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
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 From: Kathleen Smith <bounce-kathleensmith6726@tessituranetwork.com> Sent: 5/7/2013 12:54:26 AM 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 This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you! Explore the 2013 season at www.aco.com.au/buy/subscriptions This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. The ACO is not responsible for any changes made to a document other than those made by the ACO or for the effect of the changes on the document's meaning. The ACO accepts no liability for any damage caused by this email or its attachments due to viruses interference, interception, corruption or unauthorised access.
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
From: Kathleen Smith <bounce-kathleensmith6726@tessituranetwork.com> Sent: 5/7/2013 12:54:26 AM