Sage 500 discontinued

We are currently using Sage 100 and want to move away from a proprietary database.  We were looking into Sage 500.  In all my researching someone just mentioned to me that Sage 500 has been classified as  a ‘sunset’ product meaning… while companies can still buy it, Sage will not continue developing it. 

Anyone have more info on this?  We are happy with Sage 100 except for the Providex database and low emphasis on manufacturing.

Thanks

P.Park

Parents
  • 0

    Lots of great information here to mull over.   I am beginning to wonder what the advantage of having sql database is.  If someone has developed a providex based custom module for us, would there had been any advantage id our database was sql insofar as the portability of moving the maintenance and enhancement of the code to another programmmer?  I have always felt a bit like a prisoner to a single/sole Providex programmer and feel stuck.  Is this myth or fact that having a sql product would give us more flexibility in finding programmers for add on modules.

  • 0 in reply to paula2013

    To have a true add-on, the underlying database upon which it resides is less significant than having access to the application layer's source code itself. There are plenty of reputable Master Developers for both Sage 100 and Sage 500 who have access to the respective program's source code.

    Can you cite specific functional shortcomings of Sage 100 for which your company needs to solve? I think that's the real crux of the matter that has not yet been addressed in this thread.

Reply
  • 0 in reply to paula2013

    To have a true add-on, the underlying database upon which it resides is less significant than having access to the application layer's source code itself. There are plenty of reputable Master Developers for both Sage 100 and Sage 500 who have access to the respective program's source code.

    Can you cite specific functional shortcomings of Sage 100 for which your company needs to solve? I think that's the real crux of the matter that has not yet been addressed in this thread.

Children
  • 0 in reply to D.Hart

    The real cruz is that the head of the company wants "modern software" that will take us into a growth cycle and that would have many years of stability.  He is under the impression that MAS200, Sage 100, is old school with it's Providex database and we would have more flexibility with possible inhouse manipulation of data for analysis or development of software with a open database, sql.   Since I am a licensed trained MAS200 support person i use Visual Integrator, Custom Office, etc.  But I am not a sql programmer.  The other major issue, is that MAS200 (Sage 100) does not have an emphasis in manufacturing.

  • 0 in reply to paula2013

    Paula,

    I've worked as a developer extensively in both products.  I believe there are quite a few different issues here:  1.  Data Manipulation/Business Intelligence.  I think Sage 500 likely has MUCH BETTER tools for this because it is SQL.  That said if you work with a reseller/developer you'll be able to get almost the same from Sage 100 because they'll just extract the data and put it into your SQL product.  I think native SQL is the better way to go especially because Sage 500 has a great data design.

    2.  You need better manufacturing software.  Sage 500 is said to be better here than Sage 100.  Sage 500 also has some strong 3rd party products..  Overall Sage 500 is probably the better choice.  Of course due diligence is in order.

    3.  You don't know SQL and might be worried about your personal future.  There are tons and tons of free training on SQL.  Additionally sites like Pluralsight offer on demand courses which are generally top notch.

    4.  Is 500 going away?  Sage is committed to it for at least the next 6 years though there is no doubt it isn't getting much attention compared to X3 for example.

    Good Luck,

    John

  • 0 in reply to JohnHanrahan

    I would also add to John's analysis that SQL Server databases have the room to grow and are only limited by hardware and certain licensing.   I'm not sure what the size limit of a Providex database is but I don't think it can compete with SQL Server.

    If hardware is an issue, I know Microsoft Azure allows the creation of VM Machines that run SQL Server which can be accessed through your local network.   I haven't tried installing Sage 500 to an Azure VM yet (future experiment), but from what I've read it should be possible. azure.microsoft.com/.../sql-server

    I would also point out that Sage 500 is very flexible in regards to building integrations to other software systems and services.  Technologies such as web services, Windows Communication Foundation (WCF), and SQL Server Integration Services (SSIS) are just a few of the ways you can import or export data from Sage 500.  Sage 500's Data Migrator is a very powerful tool for doing imports using SSIS.  So if you need to have integrations to other systems, Sage 500 can do the job.