Sage 300 ERP Best Practices in Cloud Workspace

This Knowledge Base article will simply cover how the program is set up, where the data is stored, what Swizznet is backing up, and what you need to do as the partner. 

Administrative Access

When you log in to the server using the management portal (, you are accessing the server as a local administrative user. You will have full admin rights to the server(s) for that customer. You should 


Sage 300 ERP should be installed to the default location on the C:\ drive. The data should be stored at: C:\data\COMPANYCODE\Sage with all the proper permissions configured as per Sage's system requirements. 

Considerations: If you want to privatize the share more, and have it be 'invisible' to end users, but still accessible programmatically, you can make a share at the c:\data\* level. Create your data folder and then set up the NTFS permissions and share permissions according to Sage's requirements. This way it is not in the H:\ drive that gets mapped for all users, but they'll still be able to access it via UNC path.


Mapped Drives

We map folders out as drive letters for the customers, where as the Admin users (partners) will not see them the same way. Here is a list of our default mapped drives, and what their purpose is. 

Z:\ - Within Cloud Workspace, every user will get a personal drive that is only visible to them. This can be used to store private documents, etc. C:\home\companycode\username

H:\ - This mapped drive is the shared data location for the server. All users will have access to this, and this is a place to store common folders, documents that all of the users must access, etc. The physical location of this share is, C:\data\companycode\

F:\ This mapped drive is the location where data uploaded via FTP will be stored. Typically this would be used during the migration period. C:\ftp\companycode\

*Our default Sage 300 ERP builds have 100GB of disk space, but this can be increased by contacting sales. Please note, that we can expand data drives, but not shrink them. 


You can create shares as needed on the server. We understand that customers needs vary and that some of your users may be used to browsing through the company files, where as some may not be technical enough to do so. Please note, if you create a share, ensure that Everyone is given Full Control on the Share permissions as well as the Security permissions. This is required by Sage and should be used in most circumstances.

Accessing SQL

If you have requested SQL, we will have an SA user created within SQL for you to access the server. The password is in a text file on the server, located in C:\Software\SA Password.txt. This will allow you in as SA. You can manage the customer using this login, or grant yourself sysadmin rights within SQL Sever Management Studio/Sage Database Administrator. We already have Knowledge Base Articles for adding admin users, as well as normal Sage users. Those are linked below.



Our backups run nightly and retain 30 days of data. We do nightly full machine backups and in the case of Sage 300 ERP, we backup the SQL databases for restoration. Some of our partners want to do their own SQL maintenance plans and drop the SQL backup (.bak) files onto the disks - and then our full system will grab them, rather than using our SQL backup Agent.




Article is closed for comments.