Best practices for managing old accounts and sites.
When dealing with old accounts/sites in Service Desk Plus MSP (SDP MSP), it's essential to follow best practices to maintain a clean and organized database. Managing old accounts/sites efficiently can help improve performance, reduce clutter, and ensure that the system remains responsive.
Here are some best practices to handle old accounts/sites in SDP MSP:
1.Regular Database Cleanup: Conduct regular database cleanup activities to remove old and inactive accounts/sites. Archiving data can be useful if you need to retain historical information for reporting or compliance purposes while keeping the active database clutter-free.
2.Define Retention Policies: Establish retention policies to determine the duration for which old data should be retained in the system. For example, you might decide to retain closed accounts/sites for a specific period (e.g., six months) before archiving or deleting them from the database.
3.Review and Identify Inactive Accounts/Sites: Periodically review the list of accounts/sites to identify those that have been inactive for an extended period. Based on your retention policies, consider archiving or removing these inactive records to free up database space.
4.Data Backup: Before performing any cleanup or deletion of old accounts/sites, ensure that you have a reliable data backup strategy in place. This backup will allow you to restore the data in case any issues arise during the cleanup process.
5.Notify Users: If possible, inform users or stakeholders about the cleanup process and its impact in advance. This communication helps manage expectations and avoids surprises when old data is archived or removed from the system.
6.Review Customizations and Workflows: If you have any customizations or workflows that involve the processing of accounts/sites, review them to ensure they handle old and inactive data appropriately.
7.Document Changes: Document any changes made to the database, including archiving, deletion, or migration of old accounts/sites. This documentation will help in troubleshooting and maintaining the system in the future.
8.Protect User Privacy: Remove or anonymize personally identifiable information when retaining historical data.
9.Version Upgrades: Keep Service Desk Plus MSP up to date with the latest versions and patches. New releases often include performance improvements and bug fixes that can enhance the overall efficiency of the system.
By following these best practices, you can effectively manage old accounts/sites in Service Desk Plus MSP and maintain a well-organized and high-performing database.
New to ADSelfService Plus?
Related Articles
Best practise to configure Sites to follow same configurations using Site refer sites feature
Let me explain with some examples : In case , if the Accounts / Sites are geographically distributed and you want to configure dedicated technicians for them , we can make use of Site-Refer-Sites feature (similar to default settings but applicable ...Query to List down Account and corresponding sites and its requesters (MSSQL & PGSQL)
*Tested in builds from PGSQL (14300) or MSSQL (14306) *Applicable for 14500 builds For Accounts and Site: select adef.org_name "Account",sdo.name "Site Name" from accountdefinition adef left join accountsitemapping asm on adef.org_id=asm.accountid ...Configuration of Sites_Best Practice
To configure multiple sites with customized / similar configurations, We have multiple options while creating a site. Refer Default settings: If you have common configurations for all your sites. Create those sites with Refer settings. This will ...How to make a site(s) Inactive in SDP MSP
Note: As per the design, if you remove a site which is already associated with a request, the same will be moved to Inactive sites to maintain the service history of the site. Steps to make a site Inactive in SDP MSP: 1) Select the site or sites that ...Query to show technicians associated accounts, sites and Support groups - (MSSQL & PGSQL)
Tested in Build PGSQL (14300) or MSSQL (14306) 1.Technicians and associated Accounts/Sites: select aau.User_id, aau.first_name "First Name", sdu.lastname "Last Name", aal.name "Login Name", AaaContactInfo.EMAILID "Email Address",sdu.jobtitle "Job ...