x Want to participate? Join the group to interact
Options
  • Replies 7 replies
  • Subscribers 106 subscribers
  • Views 2247 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
92
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
963
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Kevin M

SQL mdf / ldf locations wrong after migration (v2020)

Posted By

I did a test migration last night (v2017 Premium to v2020 Premium, same server, both SQL instances are local), with the new instance's default data directory changed to the E-drive.  When I installed v2020, the MAS_ABX and MAS_SYSTEM files were properly in the E-drive path.

However, when I ran the migration the company databases had their mdf / ldf located on the C-drive, and MAS_SYSTEM had it's files moved to the C-drive too.

Now, when I created a test company, the mdf / ldf are properly on the E-drive, so SQL is fine... just the migration program seems to cause a problem with the restored file locations.  Is this a known issue?

I have moved the files, and can deal with this manually again when doing the Live upgrade, but in situations when C-drive space is not abundant this could seriously cause problems.

  • Hi @,

    Thanks for reaching out. Did you ever find a resolution to this issue? If you are still looking for guidance, please let us know and we can try to point you in the right direction or suggest some resources or next steps.

    Warm Regards,
    Erzsi

  • in reply to Erzsi_I

    Hi Erzsi,

    I did the upgrade and dealt with the problem manually.  I don't need further information.

    I posted it here to let Sage know of the problem, and hopefully fix it (before someone tries to upgrade without enough space on the C-drive, crashing the server in the process). 

    I am not 100% sure (since I didn't install SQL for this upgrade) but expect SQL was installed with default paths on C... with the path settings changed later, and the Sage migration somehow not using the Active data file paths for SQL.

  • in reply to Erzsi_I

    Very good explanation. Thanks for your article  MyGroundBiz Login

  • It happened again, with an upgrade to v2020.1 Premium (from 2018 Premium). 

    There is a flaw in the restore code for the migration program.  The paths used are wrong.  It's like the program uses the original data paths set when SQL was first installed, not the correct current / active data paths.

    MDF should have gone to E, with LDF onto F.

    Yet the migration restore put the files on C!?!?

    And it crashed.

    Please record this as a defect and correct the migration program.  I am able to bypass it this time, but that won't always be the case.  The migration should NOT crash, when there is plenty of space available on the drive(s) SQL is set to store MDF / LDF files.

  • Hi Everyone,

    A fix for this issue is targeted for Sage 100 Premium 2021. However, there is a fix available for version 2020. 

    Check out Knowledgebase Article 'Sage 100 Premium Company and MAS_System databases are copied to SQL Instance Root Directory Data folder, rather than default Data and Log folders, when migrating to Sage 100 Premium 2018-2020' (ID: 91191) on Sage Knowledgebase for additional information.

    Thank,

    Nathan S.
    Sage Support Analyst

  • in reply to NateSage100

    Excellent.  Thanks for the update Nathan.  It's great to know there is something available when the Live server truly doesn't have enough space on C:...

    Note: I did a migration on Monday (different customer / server) where I noticed the bad paths, had SQL reinstalled (with the alternative directories set during the SQL install), and things worked fine.  It seems to only happen when the data paths are changed after the initial SQL install.

  • in reply to NateSage100

    Hi Nathan,

    Can you tell me if this problem (of the migration programming using the wrong data path) exists on the source side too? 

    I am upgrading Premium 2020 to Premium 2023, and received an error where the source file backup was being saved on the C-drive (not a lot of space), when the source system's SQL paths are on the E-drive (which has plenty of space).

    FSSERP01 is the source server (which has both Sage and SQL installed).

*Community Hub is the new name for Sage City