|
I am dealing with a SQL Anywhere 16 database where approximately 46G out of 50G total disk space resides in the extension pages supporting one single column in one single table. Needless to say, dbvalid.exe spends [cough] a lot [/cough] of time on that table. What is the easiest way to set up a validation process that fully validates everything except that column, or that table? There are approximately 200 tables in the database. I am happy to run dbvalid.exe multiple times, BUT not so happy having to maintain a dbvalid -t [ object-name, ... ] list of tables to include, rather than exclude... ...and is it even possible to code 199 table names in the [ object-name, ... ] list? ( I know, The Watcom Rule says "Yes!" :)
|
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 12 May '17, 16:04
question was seen: 1,064 times
last updated: 13 May '17, 08:15
What about SQL-based validition with a FOR loop excluding that table when building VALIDATE TABLE statements dynamically?
AFAIK we had discussions here with John about what DBVALID option correspondends to what VALIDATE CHECKSUM/DATABASE/TABLE/INDEX statement run...
Yours is a good answer, and it might even be the "easiest way", but... dbvalid -xt [ object-name, ... ] is what I really want... sigh :)
I will wait (in vain perhaps) for something "easier", then turn your comment into an accepted answer.