• Replies 9 replies
  • Subscribers 337 subscribers
  • Views 82 views
  • Users 0 members are here
Related

Extraction Set Performance

Andrew Robertson
$organization

One of our users has created an Extraction Set that is taking a very long time to complete (like 3-4 hrs). We have no other performance issues with running queries etc., in fact performance across the database has been pretty snappy. This extraction set returns something like 20,000 rows and is linked to an Output Set.

Has anyone else run into issues with Extraction Set performance? I started to do a little digging, but didn't want to spend too much time on this if this is a known issue across multiple organizations (like T-Stats build time for instance).

Thanks!

 

 

 

Parents
  • $organization

    We’ve had some issues here as well and have found that saving the file as a .csv works much better than .xls.    Not sure that will solve your issues but it made a difference here.

     

    Michelle Usadel
    Tessitura Application Specialist | The Phoenix Symphony | Tel.  602-452-0441 | Fax. 602-253-1772
    www.phoenixsymphony.org | 1 N. 1st Street, Ste. 200, Phoenix, AZ 85004
     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Christine Kohls
    Sent: Tuesday, November 15, 2016 2:21 PM
    To: Michelle Usadel <musadel@phoenixsymphony.org>
    Subject: Re: [Tessitura Technical Forum] Extraction Set Performance

     

    Hello,

    We just experienced this same problem. A 20K output set took more than 8 hours to process. We were able to reduce the time by running the output set directly on our server vs. a client PC.

    Best regards, 

    Christine Kohls

    Director of Development

    The Cleveland Museum of Natural History

    ckohls@cmnh.org

    From: Andrew Robertson <bounce-andrewrobertson2168@tessituranetwork.com>
    Sent: 11/15/2016 3:35:35 PM

    One of our users has created an Extraction Set that is taking a very long time to complete (like 3-4 hrs). We have no other performance issues with running queries etc., in fact performance across the database has been pretty snappy. This extraction set returns something like 20,000 rows and is linked to an Output Set.

    Has anyone else run into issues with Extraction Set performance? I started to do a little digging, but didn't want to spend too much time on this if this is a known issue across multiple organizations (like T-Stats build time for instance).

    Thanks!

     

     

     




    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!
Reply
  • $organization

    We’ve had some issues here as well and have found that saving the file as a .csv works much better than .xls.    Not sure that will solve your issues but it made a difference here.

     

    Michelle Usadel
    Tessitura Application Specialist | The Phoenix Symphony | Tel.  602-452-0441 | Fax. 602-253-1772
    www.phoenixsymphony.org | 1 N. 1st Street, Ste. 200, Phoenix, AZ 85004
     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Christine Kohls
    Sent: Tuesday, November 15, 2016 2:21 PM
    To: Michelle Usadel <musadel@phoenixsymphony.org>
    Subject: Re: [Tessitura Technical Forum] Extraction Set Performance

     

    Hello,

    We just experienced this same problem. A 20K output set took more than 8 hours to process. We were able to reduce the time by running the output set directly on our server vs. a client PC.

    Best regards, 

    Christine Kohls

    Director of Development

    The Cleveland Museum of Natural History

    ckohls@cmnh.org

    From: Andrew Robertson <bounce-andrewrobertson2168@tessituranetwork.com>
    Sent: 11/15/2016 3:35:35 PM

    One of our users has created an Extraction Set that is taking a very long time to complete (like 3-4 hrs). We have no other performance issues with running queries etc., in fact performance across the database has been pretty snappy. This extraction set returns something like 20,000 rows and is linked to an Output Set.

    Has anyone else run into issues with Extraction Set performance? I started to do a little digging, but didn't want to spend too much time on this if this is a known issue across multiple organizations (like T-Stats build time for instance).

    Thanks!

     

     

     




    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!
Children
No Data