Sage 100

BizNet with MAS 200 SQL question. Last month I installed Sage 100 Premium v2013 PU5 as a test upgrade from v430 non-sql. Live upgrade will be next month. BizNet has also been installed (by somebody else woohoo) and they have created some Financials for the customer's review. BizNet works and all is good currently. But next month I presumably remigrate system files. HOWEVER the MAS migration program actually drops the MAS_XXX database instead of merging into it (doh!). So prior to migration, I do plan to use the Generate Scripts utility in SQL Mgmt Studio to script off any BizNet specific views, stored procedures, triggers, indexes, functions, etc. That way I can run the scripts after migration to restore the BizNet stuff that it set in the MAS_XXX database. The objective is to not have to reinstall or recreate any reports with BizNet. However what I'm uncertain of is whether BizNet or the reports it creates through SQL Reporting Services, does it reference MAS_XXX by database ID instead of database name? (and if it's by ID is this something one can pay $900 to BizNet to change @ShawnSlavin :-)

I just ran into an issue with a 100 Premium customer using BizInsights. They added an additional company to 100 but couldn't report on it through BizInsights. The only thing we needed to do to make it available to BizInishts was to map report writers and drill down viewers to the new database with a db_datareader role. This being said, I don't know that additional steps will be required in your conversion. I'm not aware of any SQL components in the MAS_XXX database you need to script and save. Unless the migration drops the ReportServer database or ReportServer TempDB, you should be good to go. All the extraction and data manipulation is done through SSRS....at least that's my understanding. There are a number of really strong resources in the support department at BizNet who can confirm just make sure. Just go to the support page and enter an issue. They call back pretty quickly. (http://www.biznetsoftware.com/support/support-issue/)

BTW, all reporting is done in Excel so you won't need to recreate any reports.

Just wanted to second what Shawn said. The only BizNet piece in SQL is the Linked Server to the silent MAS ODBC DSN. Everything else is in SSRS, so it shouldn't be affected by the migration.

Shawn thank you. I'm glad to hear there are no BizNet SQL components in MAS_XXX DB. I just assumed there was. Migration definitely will not touch ReportServer database or ReportServer TempDB so that is all good too. I'll ask the BizNet person on our team to contact their Support about whether the SSRS references to the MAS_XXX database are by DB ID or by name. I'm sure SSRS is smart enough to handle all this regardless but we'll ask just to be 100% sure because I don't want any surprises at Go Live. Steve thanks. Just to be clear this is MAS SQL so there is no Linked Server to an ODBC DSN in this case. Just want to be sure SSRS will handle the change in DB ID caused by the not so intelligent MAS SQL Migration program that drops and recreates the DB.

Since this is 100 Premium, there is no linked serer or silent DSN to work with. Those are only required when working with Providex. Just make sure to grant access to the company databases.

@ShawnSlavin thank you again. This upgrade took place this weekend and the short of it is remigration dropped and recreated the MAS_XXX db's but no problem for BizNet the financials stmts still worked and showed the correct data.

Good to hear all worked well Alnoor. Nice to return the favor once in a while.