• Embedding an object (Create from file):

      Embedding an object in the media item places a copy of the original object (Word document, image file, etc.) into the database. When embedding objects, keep in mind that it increases the size of the database by the size of the files. For example, if you embed an image file that is 1 MB, the size of the database increases by 1 MB. If you use the MSDE version of SQL Server, Microsoft limits the database size to 2GB.  If you use the EXPRESS version of SQL Server 2005 or 2008, Microsoft limits the database size to 4GB.  If you use the EXPRESS version of SQL Server 2008 R2, Microsoft limits the database size to 10GB.   If you reach these size limitations, you will need to purchase a full version SQL Server Standard or Enterprise. If embedding files would unnecessarily cause you to hit the database size limitations, we recommend linking to the object instead. 
    • Linking to an object (Link checkbox):

      Marking the Link checkbox when adding a media object adds a path to the original object, instead of embedding a copy of the object in the database. As long as the linked path is valid and available, users can access the desired objects. This is the preferred option for local installs in relation to overall database performance and taking advantage of dynamic updating of object files. If a locally installed database later migrates to NXT and Blackbaud Hosting Services, we recommend running the Media Embed Utility. What is the Media Embed Utility?
    Note: All files added to the media tab in the Hosted Environment must be EMBEDDED rather than linked.  If you do not embed the media file, it will become unusable when it is deleted from the Files Folder or by other users. For more information, see How to add, edit, or delete attachments (media) in a Constituent record for Raiser's Edge or How to add, edit, or delete an object on the Media tab for Financial Edge or Education Edge.