Sage 100

2014 premium to 2017 premium data migration / upgrade. When the data migration is performed a SQL backup is performed. Then, the data conversion is run. I would prefer to bypass the Sage data migration and make the SQL backup myself. After SQL is backed up, where is it copied to? Where will Sage 2017 look to convert the data? Is this feasible, and are there any cautions to be on the lookout for? @PhilMcIntosh and @JohnnyPabian and @AlnoorCassim and @SteveIwanowski and anyone else that has a clue!

This is what I was sent on a 2014-2016 upgrade about 15 months ago

Doug you can't avoid the auto SQL backup. It will backup to either the current SQL Data folder location or Backup location which is in the registry. You can run this T-SQL on SQL 2014 server. It will create a BAK file in 1 of these 2 places: EXECUTE [master].dbo.xp_instance_regread N'HKEY_LOCAL_MACHINE', N'SOFTWARE\Microsoft\MSSQLServer\MSSQLServer', N'DefaultData' EXECUTE [master].dbo.xp_instance_regread N'HKEY_LOCAL_MACHINE', N'SOFTWARE\Microsoft\MSSQLServer\MSSQLServer', N'BackupDirectory' For me it kept backing up to the DATA directory. It takes that BAK file, copies it up to the 2017 SQL DATA directory, and RESTOREs it. For one client, I also had trouble making it complete the backup within 30 minute timeout period . But setting backup compression cut the time in half and size by more than half. Xlnt feature and recommend this regardless: ` EXEC sp_configure 'backup compression default', 1 ; ` ` RECONFIGURE WITH OVERRIDE ; ` ` GO `

Thanks Phil and Alnoor. I am pretty sure @JohnnyPabian told me at at MOTM there was a way around the data migration by backing up SQL. He was probably referring to the process Alnoor uses which is great.

@PhilMcIntosh I know the standard Sage 100 procedure to perform the data migration. Basically, Sage 100 makes a SQL backup on the source database, copies the backup and the attaches the copy to the target database. It makes me a bit nervous letting the parallel migration utility make a backup of the live source database. I would prefer to have more control over it. Ideally, manually make a backup of the source SQL and then attach it / convert the data on the target.