nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

FTP Files Location

Damon Rosenthal

We were recently relocated to Azure platform. I wanted to understand the background of this file space and the overall intend. I worked with import and exports from this space thinking the process would run faster if the data wasn't going from my local workstation to hosted db and back. I can also understand this for output of scheduled automated Queries run off hours. It appears this is not intended for warehousing or backing up data. Can someone please provide me more background on the intent here so I can better manage for our use and guide our organization on use of this FTP file space?

Find more posts tagged with

Comments

Alex Wong

@Damon Rosenthal
when you say “relocated to Azure" I'm assuming you were “Blackbaud hosted”.

FTP in Azure is the same as FTP for Blackbaud hosted, it is just a “hosted location” where exports (from dbview) is saved and can be accessed via FTP, or import file you created is saved and dbview import can access the import file. Nothing changes/special about Azure FTP vs Blackbaud hosted FTP.

RE:Queue (if you have this paid service from Blackbaud) works the same as on Blackbaud hosted vs Azure: RE:Queue will export files on schedule into the FTP folder location, and then can “read/picked up” manually by accessing the FTP locatoin (difference here is the folder structure/path is different on Azure compare to Blackbaud hosted), OR can be automated by a workflow automation platform (i.e. Power Automate).

As with Blackbaud hosting, Azure FTP is also subject to storage limit impose by Blackbaud, it is definitely not a location where you want to save a ton of files and let things go “wild”. Regular clean up is still needed to ensure you don't go over storage limit.

Damon Rosenthal

@Alex Wong
Thank you Alex for reply.

Yes we relocated as a BB hosted solution.

We do have RE Queue but have not really using it yet. Another topic and item we/I need to learn/investigate.

Generally I direct files to my local machine unless larger imports where I thought it would be faster and reduce time out issues if I used this hosted file space.

Overall, I am just trying to better understand its overall purpose/benefits so that I can come up with some direction to the team on using and managing it …. to ensure it stays organized from the cleanup I have done for the relocation.

Many processes default to this space and if you don't want to use it, you have to be intentional about updating paths for resulting files - exports, exception files, etc. i.e. ImportOmatic exception files default to this space.

Alex Wong

@Damon Rosenthal
generally saving to hosted file location is faster, especially if you are saving CSV. I don't know if much have changed, but saving CSV is “direct” so the export will do X records at a time depending on memory buffer (30 rows of record) thereby being very slow. Saving to Excel is much faster due to the export is saved completely as an excel file in temp location of hosted system before being “moved” to where you intent to save the file (local), thereby much faster.

Damon Rosenthal

@Alex Wong
ok, that is not what I would have thought, so great to know!

Dan Snyder

@Damon Rosenthal Not much to add to the great information @Alex Wong shared. I really basically only use it as a temporary “dumping ground” for my overnight automated Queue processes. You can't really open any files other than PDF there because there are no Office apps in the hosted environment.

With the launch of the Query API and Power Automate Query connector, I am trying to just go that route where I can and as I have time to update reporting with new data sources.

Damon Rosenthal

@Dan Snyder
Thank you Dan!