Querying Pastel Evolution DB directly

[BlindMelonChitlin]

I'm not a Pastel fundi, but will be doing an assessment of a client's system that at some point interfaces with Pastel. I'm not sure if the interface is electronic or manual - I still need to have that conversation. What I'm hoping to figure out in advance is whether it's easy to query the pastel evolution tables direct or are they suitably locked down? What accounts / passwords are required if not?

I recall Pervasive SQL back in the day and Microsoft SQL in some more recent versions (though I haven't touched pastel in over 12 years). What does Evolution run on these days?

Ta in advance!

 

[IndigoIdentity]

This would be possible via ODBC.

 

[BlindMelonChitlin]

OK - any idea what platform it runs on DBMS wise? What users/passwords are used? I don't imagine they are regular pastel user accounts?

 

[Kosmik]

Evolution can run on MS SQL. We have it going and I tap into it regularly for integration. Not a fan of the db structure though. If you have control of the server setup your own integration account.

 

[BlindMelonChitlin]

Evolution can run on MS SQL. We have it going and I tap into it regularly for integration. Not a fan of the db structure though. If you have control of the server setup your own integration account.

Cool, will give this a try, Ta!

 

[IndigoIdentity]

PSQL Control Center

 

[BlindMelonChitlin]

PSQL Control Center

That applies to pervasive - what flavour of SQL should I be expecting?

 

[IndigoIdentity]

PSQL CC is basically like phpmyadmin for Pervasive, which Evolution uses.

Flavour is Pervasive SQL, very similar to MS SQL but has some differences in syntax.

 

[BlindMelonChitlin]

PSQL CC is basically like phpmyadmin for Pervasive, which Evolution uses.

Flavour is Pervasive SQL, very similar to MS SQL but has some differences in syntax.

Perhaps it depends on the version - this page suggests Microsoft SQL:
http://www.sageevolution.com/

 

[Kosmik]

Perhaps it depends on the version - this page suggests Microsoft SQL:
http://www.sageevolution.com/

Depends on your installation but both companies where I've worked on it has been the ms sql flavour.

 

[PsyWulf]

Pastel evolution runs on mssql. Paster partner runs on pervasive

As for db structure its mostly straightforward

 

[schuits]

We have Pastel Evolution running here on MSSQL.

 

[Solarion]

Wouldn't the DB be admin locked? How would you get in to view the objects?

 

[Kosmik]

Wouldn't the DB be admin locked? How would you get in to view the objects?

Depends if he has rights over the server. Server admin can control the databases within itself.and of course he can then create or use accounts however he feels but it's always a good idea to create an integration account that can read only from a db not your own.

 

[halfmoonforever]

From an audit perspective you shouldn't be querying or accessing the financial database without some kind of SEO/API as an intermediary. You can possibly open a big can of worms from that perspective and can be held liable for any "dealings" that are not considered legal

 

[Kosmik]

From an audit perspective you shouldn't be querying or accessing the financial database without some kind of SEO/API as an intermediary. You can possibly open a big can of worms from that perspective and can be held liable for any "dealings" that are not considered legal

There is a API that can be purchased for Evo but also the setting up of a read only sql account for access still conforms to most audit guidelines. It's when one starts manipulating data that the process comes into question.

 

[halfmoonforever]

There is a API that can be purchased for Evo but also the setting up of a read only sql account for access still conforms to most audit guidelines. It's when one starts manipulating data that the process comes into question.

Even from a read perspective, you don't necessarily want to give someone read on all your financial data, and there needs to be a control element to be able to separate what users (or applications) can read from your GL (for example)

It might be a bit more lax when it comes to reading of data, but can still contravene something like POPI

 

[Kosmik]

Even from a read perspective, you don't necessarily want to give someone read on all your financial data, and there needs to be a control element to be able to separate what users (or applications) can read from your GL (for example)

It might be a bit more lax when it comes to reading of data, but can still contravene something like POPI

Yes, that's fully controllable via normal sql user rights and permissions, not sure what the issue is? POPI is the protection of information, the people who have access to the relevant accounts would be controlled via the company, same as if they had a standard Pastel account.