Geek Answers Handbook

ODBC Progress Problem with Sql-width (DBTool?)

I was assigned to get some data from a third-party progress database. The problem is that some tables report the error "The column <column> in the table <table> has a value that exceeds its maximum length or precision (7864)."

In some cases, GoogleDog is a problem with the width of the SQL in the database, and that starting DBTool can fix this. http://progress.atgnow.com/esprogress/jsp/AnswerControls.jsp?directSolutionLink=1&tabs=true&docPropValue=p24496

The problem is that the third party that manages the progress database does not want to know - they say that it can damage the database. Since I know nothing about anything (especially about Progress), I can not resist their arguments.

To the questions:

  • Do they have a valid argument against this tool not working?
  • If they maintain their position, do I have any other options open to me? Keep in mind that I do not know the first thing about Progress.
+4
source share
1 answer

Your third party does not know. DBTool is the standard way to solve this problem and has been provided for this purpose. Running dbtool is extremely common and usually starts automatically periodically (monthly, usually good).

They can be confusing "dbrpr". Which can reformat blocks and other funny things that will definitely get you in trouble if they are not used correctly.

You can almost certainly manage it yourself or without their cooperation. All you need is a dba id and password. I could be wrong, but 98% of the time when dba userid is "sysprogress", and it is probably used in ODBC connections. If you configured them, you probably know the password (or you can easily get it).

(If they did not run dbtool, then they probably also did not use UPDATE STATISTICS, which probably means that the performance is very poor. The Progress SQL engine uses a cost-based optimizer and without any statistics do it very well work, but this is fodder for another matter.)

+2
source

More articles:


All Articles