Sabashni,
It doesn't look like there is many things changed between the 2 versions, check out the schema change log:
https://my.inin.com/products/cic/DatabaseSchemaChangeLibrary/ININ_2017R4_P00/SQL/CIC%5EMSSQL%5EININ_2017R4_P00%5EININ_2019R2_P04.htmlMaybe there is a bunch of data in one of the tables which changed between the versions and the update is causing the database transaction log to grow? I've done a fair share of upgrades and have never had a DBA complain about the transaction log growing too large after a upgrade.
Maybe there is something else going on with the database as you mention the customer is using simple backups which I don't think I have ever had a customer have their transaction log set to simple on a production database. Do you know how often the customer is doing database backups, when they rebuild indexes and statistics, as well as how big the database is today? Also how large is the transaction log getting on the update?
Thanks,
------------------------------
Mark Tatera
ConvergeOne
Opinions are my own and not the views of my employer. Any suggestions or programming changes I suggest come with no warranty and should be tried at your own risk.
------------------------------
Original Message:
Sent: 07-01-2019 08:04
From: Sabashni Moodley
Subject: 2019R2 IC Build Script creating large SQL Log files
Hi
We have a customer that we are upgrading from 2017R4 to 2019 R2 and our DB is set to simple although we are still generating a large of transaction logs when running the IC build script.
any one experienced this as well?
#Unsure/Other
------------------------------
Sabashni Moodley
Elingo (Pty) Ltd
------------------------------