Using SQL Server Management Studio To Work With Sage 100

Ok,

So I'm new to this forum, so I apologize in advance for any breach of protocol.

Basically, I have set up a DSN on my server running MS SQL, and it works fine.  I can see all of my tables (but not fields) for Sage 100 Advanced ERP in SSMS - Great! However, it appears that I can't use the typical functionality of SSMS to see the fields in the database, or to build new views for the Sage ProvideX tables, but that I must actually write the SQL code (which does work).  I'm using Sage Advanced ERP 2013 (Upgrading to 2016 soon), and SQL Server Managament Studio 2014.  My DSN and SQL are both 64-Bit.

My question, is this typical with a Server Linked Sage database?  Part of the reason I wanted to use SSMS was to easily view the database and create the views graphically rather than having to write the SQL code manually.

My goal in creating the views is to create a subset of tables that I work with ALL the time in conjuction with custom Crystal Reports, and to speed up those reports.  In particular, some of the tables I regularly report on include AR_InvoiceHistoryHeader, HistoryDetail, CI_Item, ProductLine and so on.

I am a Crystal Reports manic, but I admit, I'm pretty new to SQL, so any observations, suggestions, or questions would be welcome!

THANKS everyone.

Parents
  • 0

    Personally instead of using SQL Server, I use PostgreSQL because it's faster and cheaper (open source).  It also takes significantly less resources (I run it right on my SAGE 100 server).  To replicate the data, I wrote a program that allows you to replicate the table structures in PostgreSQL and then allows you to define how frequently you want each table updated.  Once the auto-replicate mode is selected, it runs continuously updating the tables once they have "expired" per your settings.  I have no problem sharing the source code.  It's a .NET program, though I wrote and compiled it in Sharp .NET, because it too is free and open source.

Reply
  • 0

    Personally instead of using SQL Server, I use PostgreSQL because it's faster and cheaper (open source).  It also takes significantly less resources (I run it right on my SAGE 100 server).  To replicate the data, I wrote a program that allows you to replicate the table structures in PostgreSQL and then allows you to define how frequently you want each table updated.  Once the auto-replicate mode is selected, it runs continuously updating the tables once they have "expired" per your settings.  I have no problem sharing the source code.  It's a .NET program, though I wrote and compiled it in Sharp .NET, because it too is free and open source.

Children