sqldump?
- Thread starter HPM75
- Start date
Non-Progress developers wants to run queries against the data without using ODBC.
Therefor the recommendation is to use sqldump and load the data in to a SQL Server DB prior to running queries against it.
The thought is to set up a process for dumping the data from tables involved on a regular basis.
Therefor the recommendation is to use sqldump and load the data in to a SQL Server DB prior to running queries against it.
The thought is to set up a process for dumping the data from tables involved on a regular basis.
TomBascom
Curmudgeon
That seems like an awful lot of work just to avoid an ODBC connection. Especially if you're going to be doing it on a regular basis. What is the objection to ODBC?
On the other hand SQL users running "queries" (presumably ad-hoc queries?) are notorious abusers of databases so getting them off in their own little world where they can do no harm to the performance of the production database is generally a good thing. Usually I would do that by giving them their own reporting db. Perhaps by restoring from the nightly backup or perhaps by using replication. That would still require an ODBC (or JDBC) connection though. The other approach is to create a "data warehouse" extract and load it into whatever you are using for that purpose. Those sorts of things usually only want new and changed data though -- not whole tables. And that generally requires at least a little bit of programming.
On the other hand SQL users running "queries" (presumably ad-hoc queries?) are notorious abusers of databases so getting them off in their own little world where they can do no harm to the performance of the production database is generally a good thing. Usually I would do that by giving them their own reporting db. Perhaps by restoring from the nightly backup or perhaps by using replication. That would still require an ODBC (or JDBC) connection though. The other approach is to create a "data warehouse" extract and load it into whatever you are using for that purpose. Those sorts of things usually only want new and changed data though -- not whole tables. And that generally requires at least a little bit of programming.