Search results

Progress has a product for sale called pro2sql that will use replication triggers in 10.2B to replicate data from OpenEdge to MS SQL. You could write your own code using triggers or database auditing, would make it a lot easier if the table you are trying to replicate has a unique index...

forget binary, only works if you are loading back into OE. Use an ASCII dump to export data from OE and use bcp to load data back into MS SQL.

Do you have a 4gl development license to just run an ascii dump of the OE database into flat files and then import into MS SQL ? Another option if there isn't a 4gl dev license would be to use SQL utilities to dump data into flat files and then import into MS SQL. If you can, obtain the latest...

At the 2017 PUG challenge, it will be revealed that Mike is Mr Bascom's pen name.

Need to provide what your startup parameters are

A bit unrelated to the original post, but see you are running 9.1 Progress and mention a 2TB database. There are some storage limits for Type I storage areas, just in case you aren't aware... Search Progress support for Maximum Storage Area for Type I Storage Areas.

If you are new to OE / Progress databases and are more familiar with MS SQL, you might consider exporting the data from OE and loading it into MS SQL to do your data investigation.

11.7 is now released. Progress just held a Webinar to discuss the new features. The session was recorded so it should be made available for viewing soon.

The db has become corrupted for unknown reasons... is it safe to apply the entire contents of the busy AI file ? Doing it manually you could back up 30 seconds or so. Not sure how that could be scripted.

if you are trying to purge over 50% of a table, i have had better luck with saving off the data I want to keep. Drop the table and then load the data back in. if you are using Progress 9, then you probably don't have access to SQL drop table command, so you would need to rename the table and...

I believe retry option allows rfutil to ignore the timestamp mismatch...

We have people that like to see GUI interfaces so we use OEM as a way to get trending and secondary monitoring. We had to allocate 4gb of memory to our admin servers to keep them from shutting down with some java memory issue. @Cringer - OEM has some diagnostic pages that will help you see the...

When we get data errors after copying a database, it was because someone connected to the source database while we were copying it. Might want to check the source db's log while the copy was running.

By chance do you sit beside Mike ? look at sqldump since you don't have the 4gl dev license.

Linux and SCO would need the same Endian Byte Order big endian vs little endian. But like Rob stated, I don't think a Progress install for one OS would open a database created on a different OS. You might have better luck trying to find someone who has a functioning SCO server who would be...

In my experience with OE 10 an online table move required the BI to grow to 10 times the tablesize because the work is done in a single transaction. I didn't try online tablemoves for any table larger than 200mb due to bi growth and the performance impact to other processes while the tablemove...

different progress utilities in $DLC/bin call the _mprshut executable.

If possible get SP08 for 10.2B - there are some significant performance improvements. verify your admin server is running and if you specified a different port you'll need to include that in the fathom query. ps -ef | grep Dsun should find the process. it helps if the same user starting fathom...

if you chose to use idxactivate, in my experience this utility runs faster with the database online vs running it in single user mode. As a rule, we add all indexes as inactive and then activate with idxactivate, because we ran into the situation you described.

If there is a date field you can use to identify the records and existing records are not updated, then just dump the records up to a certain date ahead of time. For example dump all records more than 2 weeks old and start loading them into the new environment. Then on the migration weekend...