Best Practices in RAMP downloads. Output Sets

I’m helping out over at Liberty Science Center for my current Residency.  They are in the process of moving onto RAMP from a self-hosted solution.  They have been accustomed to doing moderately sized Output sets.  (A few 10s of thousands of records.)  Saving as MS Excel to their hard drives.  Then edit the results from there.  On RAMP they are running into extreme slowness 10 or more minutes when they try to save the MS Excel output from a report to their local (on site) drive.  Is this RAMP normal?
 
The Scenario
1. Build a list with 10,000 constituents
2. Create an Output Set with 10-20 columns
3. Run Execute an output set  (This runs just fine)
4. Save and MS Excel with an onsite disk selected.  (Like the Local C Drive)
 
This take 10 or more minutes.  Often does not appear to complete, and user kills the application.
 
If I pick a drive that is local up on RAMP.  This save runs at normal speed.
 
Have you seen this on RAMP?
Do you have a workaround or best practices to tell users?
We believe that this happens with trying to save the results of any large Report across CITRIX.  
--Tom
Parents
  • Former Member
    Former Member $organization

    We encountered this issue trying to save into an Excel file from an extraction.  Exactly due to the same reasons, we started to use the EXTRXXXX file automatically saved by the extraction, instead of saving into Excel.  You need to choose "File" as "Destination" instead of "List", and the extraction saves the file as EXTRXXXX in RAMP in the  Impftp.lnk//Extract folder,  where XXXX is the extraction number.  I believe the file is in CVV format, which can easily be saved to the local machine afterwards.

    I did not inquire with RAMP at that time,  but this problem predates Citrix in our case.  It can still be due to a 2X/Citrix protocol issue, but I suspect that the length of the file and virus protection on our end may be causing a timeout issue.

    We never tried to save files into Excel directly after moving to Citrix.  I would be curious to know, what RAMP has to say, if you decide to contact them.

  • We have already contacted the RAMP migration team.  We are waiting for responses.

Reply Children
No Data