Recently we tried to use -SQLWIDTHUPDATE ON parameter on our database but our application team does not like behavior. Currently once this parameter is ON , client connected gets truncated data in first connection and then in next connection it gets correct data. Previously the client would fail, now clients get truncated (BAD) data. So we switched off parameter again because of data quality issues.
New option to this should be that when this parameter is ON - client gets disconnected in first attempt but in next attempt it gets correct data. This will avoid data quality issues and DBA need to adjust SQLWIDHTS manually.
Why this is not a option in this design ?
Our Application Team rejected this feature due to data quality issues.
Can this be added as a option to this and related utilities including ADT.