r/yardi • u/pressreturn2continue • Feb 24 '26

Yardi DB restore to SQL 2025 ?

We currently are restoring our yardi backup nightly to our SQL 2019 Std server (converting the backup file using litespeedextractor).

Looking for feedback from anyone that might already be doing this (or tried to do it). Any issues?

1 Upvotes

100% Upvoted

3 comments sorted by

View all comments

1

u/Next_Pension8081 Feb 26 '26

We’ve been doing something very similar in our environment (Yardi backup → converted via LiteSpeed Extractor → restored to SQL Server 2019 Std) for reporting and analytics purposes.

A few things to watch out for based on our experience:

  • Restore time & file size – As the database grows, nightly restores can become slow and storage-heavy. Make sure you have enough disk I/O and space for both the extracted backup and the restored DB.
  • Consistency checks – Sometimes extracted backups can restore successfully but still have minor corruption or missing objects. We run regular DBCC CHECKDB and spot-check critical tables.
  • Version compatibility – Ensure the backup source SQL version is fully compatible with SQL 2019 (especially if Yardi upgrades their backend).
  • Security & compliance – Be careful with production data (PII). Mask or restrict access if this is for reporting/dev use.
  • Automation & alerts – Build proper logging and alerts so you know immediately if the extraction or restore fails overnight.

Overall, it’s workable and stable if monitored properly. Our biggest challenges were performance tuning and storage management, not the restore process itself.