Replicate Sage 200 Data from PowerShell



Write a quick PowerShell script to query Sage 200 data. Use connectivity to the live data to replicate Sage 200 data to SQL Server.



The CData ODBC Driver for Sage 200 enables out-of-the-box integration with Microsoft's built-in support for ODBC. The ODBC driver instantly integrates connectivity to the real Sage 200 data with PowerShell.

You can use the .NET Framework Provider for ODBC built into PowerShell to quickly automate integration tasks like replicating Sage 200 data to other databases. This article shows how to replicate Sage 200 data to SQL Server in 5 lines of code.

You can also write PowerShell code to download Sage 200 data. See the examples below.

Create an ODBC Data Source for Sage 200

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

  • Schema: Determines which Sage 200 edition you are connecting to. Specify either StandardUK or ProfessionalUK.
  • Subscription Key: Provides access to the APIs that are used to establish a connection. You will first need to log into the Sage 200 API website and subscribe to the API edition that matches your account. You can do so here: https://developer.columbus.sage.com/docs/services/api/uk. Afterwards, the subscription key may be found in your profile after logging into Sage 200.

Connect to Sage 200

The code below shows how to use the DSN to initialize the connection to Sage 200 data in PowerShell:

$conn = New-Object System.Data.Odbc.OdbcConnection $conn.ConnectionString = "DSN=CData Sage200 Source x64"

Back Up Sage 200 Data to SQL Server

After you enable caching, you can use the code below to replicate data to SQL Server.

Set the following connection properties to configure the caching database:

  • CacheProvider: The name of the ADO.NET provider. This can be found in the Machine.config for your version of .NET. For example, to configure SQL Server, enter System.Data.SqlClient.

  • CacheConnection: The connection string of properties required to connect to the database. Below is an example for SQL Server:

    Server=localhost;Database=RSB;User Id=sqltest;Password=sqltest;

The SQL query in the example can be used to refresh the entire cached table, including its schema. Any already existing cache is deleted.

$conn.Open() # Create and execute the SQL Query $SQL = "CACHE DROP EXISTING SELECT * FROM " + $Banks $cmd = New-Object System.Data.Odbc.OdbcCommand($sql,$conn) $count = $cmd.ExecuteNonQuery() $conn.Close()

The driver gives you complete control over the caching functionality. See the help documentation for more caching commands and usage examples. See the help documentation for steps to replicate to other databases.

Other Operations

To retrieve Sage 200 data in PowerShell, call the Fill method of the OdbcDataAdapter method. To execute data manipulation commands, initialize the OdbcCommand object and then call ExecuteNonQuery. Below are some more examples commands to Sage 200 through the .NET Framework Provider for ODBC:

Retrieve Sage 200 Data

$sql="SELECT Id, Code from Banks" $da= New-Object System.Data.Odbc.OdbcDataAdapter($sql, $conn) $dt= New-Object System.Data.DataTable $da.Fill($dt) $dt.Rows | foreach { $dt.Columns | foreach ($col in dt{ Write-Host $1[$_] } }

Ready to get started?

Download a free trial of the Sage 200 ODBC Driver to get started:

 Download Now

Learn more:

Sage 200 Icon Sage 200 ODBC Driver

The Sage 200 ODBC Driver is a powerful tool that allows you to connect with live data from Sage 200, directly from any applications that support ODBC connectivity.

Access Sage 200 data like you would a database - read, write, and update Sage 200 Products, SalesOrders, Suppliers, etc. through a standard ODBC Driver interface.