Is there an option available that increase database sql-width on the fly to the maxium string length in the record(s)?We run a replication and creates ddl and dump files and load them in SQL reporting database.Currently i have to run dbtool every time to prevent length errors in MS SQL server.
Is there an 10.2B08 an option available that increase database sql-width on the fly to the maxium string length in the record(s)? We run a replication and creates ddl and dump files and load them in SQL reporting database. Currently i have to run dbtool every time to prevent length errors in MS SQL server.
Flag this post as spam/abuse.
I have to insure 100% that all sql-widths are fine. Padding will not help because sometimes 3 increases to 25.
This would be a big % value for other fields -> no option.
it would be so easy for the RDBMS because it has the knowledge of everything during the update.
--Tom Bascomtom@wss.com
For SQL there is VARCHAR(MAX) but this isn't the same and has limits. (like index)
"world to stop being silly"Are you at EMEA PUG in Stuttgart, i am looking forward to discuss it with my SQL colleague.
running the ABL connections with -checkwidth option gives the user the ability to report violations as they occur or to prevent the data from being inserted if the width is in violation of the _sql-width value
Hi Richard,
I request a -checkwidth 3 :
Store the data and increase the _width field if needed
I am sure that somebody at PSC must have the same idea ...
Stefan
Rich, I think he was suggesting it as an ABL parameter, i.e., self-maintaining on the ABL side so that it was ready to go on the SQL side when needed.
Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice http://www.cintegrity.com
Still, given that one is simply updating a DB field, the chance of an ABL client doing the update and the SQL client having already started a query that will include the offending record would seem to be extraordinarily small, wouldn't it?
RE: 10.2B08: Option auto adjustment sql-width available? Reply by Libor Laubacher This is a “schema” update, not a particular record update. Or rather this would be. Hypothetically speaking. From: Thomas Mercer-Hursh [mailto:bounce-tamhas@community.progress.com] Sent: Thursday, October 16, 2014 5:55 PM To: TU.OE.RDBMS@community.progress.com Subject: RE: [Technical Users - OE RDBMS] 10.2B08: Option auto adjustment sql-width available? RE: 10.2B08: Option auto adjustment sql-width available? Reply by Thomas Mercer-Hursh Still, given that one is simply updating a DB field, the chance of an ABL client doing the update and the SQL client having already started a query that will include the offending record would seem to be extraordinarily small, wouldn't it? Stop receiving emails on this subject. Flag this post as spam/abuse. Stop receiving emails on this subject. Flag this post as spam/abuse.
1. Maybe a stupid question : Are there drawbacks to setting _sql-width to 32768 on all character fields ?
The real maximum is lower so you'd never had to update _sql-width again.