Sage Evolution - SQL Server database description

[Ushdogg]

Hi all

I am attempting to write some reports using the Sage Evolution Connector module. However, I am having a hard time finding where the correct data sits within the SQL Database. Does anyone know if there is a document that describes each table and view within the database to save me time of querying each table to find out whats in each one?

Thanks

 

[Kosmik]

Hi all

I am attempting to write some reports using the Sage Evolution Connector module. However, I am having a hard time finding where the correct data sits within the SQL Database. Does anyone know if there is a document that describes each table and view within the database to save me time of querying each table to find out whats in each one?

Thanks

Doubt it as technically the db structure is their IP. They expect you to interact with the API module but you talk about using a connector? What does that do? Evo can and does work off standard sql soyou can just leverage sql reporting services to do reports but that won't help with understanding their db structure. You can make it out, just requires a bit of work, messy though.

 

[Ushdogg]

Doubt it as technically the db structure is their IP. They expect you to interact with the API module but you talk about using a connector? What does that do? Evo can and does work off standard sql soyou can just leverage sql reporting services to do reports but that won't help with understanding their db structure. You can make it out, just requires a bit of work, messy though.

Its part of their Advanced Business Intelligence Module which allows me to write custom reports. Their connector module allows me to create "Views" from their SQL database in order for me to write reports. Writing the queries is fairly straight forward, but trying to understand where all their data sits is a pain in the ass.

 

[Kosmik]

Its part of their Advanced Business Intelligence Module which allows me to write custom reports. Their connector module allows me to create "Views" from their SQL database in order for me to write reports. Writing the queries is fairly straight forward, but trying to understand where all their data sits is a pain in the ass.

I feel your pain, I leveraged their batch import module a while ago from our ERP and that took a bit of head scratching, never mind some chaps wanting access via odbc for excel extracts. If that connector just lets you create views, I would have rather gone the way of a staging db with views and storeprocs that I could control and leverage. Doesn't solve your original issue though.

Oh and watch out for the periods, I noticed they handle it very differently to Accpac which is the other accounting db I was tapping.

 

[Raithlin]

One of the utilities in their arsenal is the Database Dictionary. Evdict.exe I think. It explains the links between the tables. It's a mainstay in my Evolution arsenal.