Page 1 of 1

Is SAGE 50 using SQLSERVER ?

Posted: 28 Jun 2016, 13:24
by linda
Hi can I ask . Is sage 50 is using SQL SERVER database ? They give us username and password for the database but they don't tell if what database did they use for the system.

Thank you in advance.

Re: Is SAGE 50 using SQLSERVER ?

Posted: 28 Jun 2016, 18:26
by brucedenney
Sage uses Structured Query Language (SQL) to talk to the database most databases do this.

SQL is a Standards based language for communicating with databases.

An SQL database in common parlance is a database where there is a separate database server, this could be any one of a number of SQL servers eg Oracle, Pervasive, MySQL or Microsofts implementation which is called Sequel or MSSQL it has deviated from the standard and it is questionable as to if it is a SQL database any more.

Why do you want to know the technology behind the product are you looking to integrate, if so you need to use the SDK.

Re: Is SAGE 50 using SQLSERVER ?

Posted: 29 Jun 2016, 03:07
by linda

Thank you for the reply. Yes I know the RDMS database and SQL, I need to know how to access the database. how to use the sdk in order to access the db, where I can find that SDK tool ?.

Thank you in advance.

Re: Is SAGE 50 using SQLSERVER ?

Posted: 30 Jun 2016, 09:37
by brucedenney
You buy the SDK from SAGE.

Re: Is SAGE 50 using SQLSERVER ?

Posted: 13 Jun 2018, 17:58
by andy636
You can transfer the Sage data to SQL server via ODBC without that SDK - Instructions here: ... -with-odbc

Re: Is SAGE 50 using SQLSERVER ?

Posted: 15 Jun 2018, 11:20
by brucedenney
In all cases the ODBC drivers are READ only so you can only read that data, you can not write data back, a one way integration is not an integration.

The app using the database could read the data directly from Sage using ODBC and/or populate the SQL database itself.

Using Micro$oft Access is one way, but has downsides.

Not sure why the tables are not being dropped and recreated in Access, I guess there is a reason.

There are other ways that do not need M$Access.

I have used Outwit to extract the data to a text file.

You can then script around that to drop and add tables to any database.

I have used this principle to do simple things, for example updating products pricing/stock levels in MySQL databases for webshops, I also used it to make a product lookup file for a bar-code scanning application, which would use the barcode to lookup the Sage Product code and then "type" that.

ODBC is a very useful tool, but not a way to do an integration, just a way to read the data.

Note that the example given was for the UK version of Sage50 not the US-Peachtree or Canadian one, I am pretty sure that there are ODBC drivers for the Canadian version and the same sort of thing could be done.