Sage 100

SQL system data is not migrating properly from test environment to production (second try) - any risk in just moving just 3 user/security SQL tables as they have spent some time on roles and users: SY_Role, SY_RoleSecurity, and SY_UserSecurity - @ShawnSlavin have you ever tried remigrating MAS_System SQL database?

Are you saying all other tables from production MAS_System is otherwise already setup and static? Then also include Sy_User, Sy_UserHistory, and Sy_Surrogate methinks. If you turned on SData in test then also Sy_ResourceRoleSecurity. There are a couple of others but not applicable on SQL. What error are you getting?

no errors when we run the migration on the system files, it runs through and acts like it's successful - it's just not replacing the data on the destination server. Now we just lost the entire F: drive where the sage app server/mas90 folder was installed. I love big IT clients - they are running Veritas Clustering - can that cause issues with Sage?

Eric look in \mas90\MAS_System folder (not db) at these files: 1. SQL Data Translation of SYSTEM nnn.log file - Look for errors in here. Hopefully you'll get clues here. 2. SY_nnnInstallation-datestamp-timestamp.log file - less likely but check it out also. Have never used VCS myself but maybe some of the other IT oriented guys have like @ChristopherWhite and @SteveIwanowski

error during conversion - ""the object GL_TableConversion0500 could not be initialized"" - after about 10 hours of data conversion from providex to SQl when it seemed as though everything was just about complete - any ideas?

the actual MAS_xxx SQl database seems to have deleted itself after 10 hrs of creating the SQl tables and conversion. Not sure if this is an IT thing since last night we lost a complete F: drive on our app server and had to move everything to E: - remond me not to schedule upgrades for Friday the 13th!

Eric, no idea regarding the cause of your troubles. Have not run into them yet. Regarding the system database, use usually use the target production environment for testing. That way we backup the System database and restore if needed after the final conversion. We haven't tried moving the 3 tables you refer to via scripting. It should work so long as you have ALL the files needed and connected. My concern would be specific to primary and foreign keys along with all referenced keys in other tables. Since I have not attempted to do this, I don't know where to point you to Eric. Just be careful and test well.

Sorry, I don't have any experience with VCS, but it sounds like something more serious is going on if you're losing drives....

yeah, major screw up on the it side and we need to reinstall and do it all again next weekend,working on a change order now :-)