0

I run a database that has a tables with several NTEXT columns that contain short lived data. We would normally only keep a few weeks of data in those tables but in an effort to reduce disk usage this was reduced down to only 72 hours.

While I expected to see some increase in backup performance, I was not expecting such a large increase. The database dropped from 105 GB of storage to 99 GB with the change in data retention. Before the change backups would roughly take 60 minutes. After the change it dropped to 40 minutes to backup.

I assumed that with a 6% reduction of storage that it would be an equal reduction in backup time, but appears to have shaved off a third of the time required for backup.

Because the majority of the data that was removed was NTEXT, does this have a much larger impact on backup performance than other data types?

I have done some searching but I haven't been able to find any connection between the two things.

Edit: I left out that these are full backups running.

noble6
  • 51
  • 2
  • 3
    [`NTEXT` is obsolete](https://learn.microsoft.com/en-us/sql/t-sql/data-types/ntext-text-and-image-transact-sql?view=sql-server-2017) – Lukasz Szozda Apr 20 '18 at 19:30
  • Well as much as I would like to do that, this is a database that was brought forward from older versions of SQL server and it was never changed. However your comment doesn't really answer my question. – noble6 Apr 20 '18 at 19:42
  • Using obsolete things+ you didn't wrtie anything about backup strategy(full/differential/log backup)??? – Lukasz Szozda Apr 20 '18 at 19:43
  • Is backup compression enabled on the server and this particular job? – Alejandro Apr 20 '18 at 19:51
  • Backup compression is not enabled for the server or the job. – noble6 Apr 20 '18 at 20:01

0 Answers0