we have an overnight job that inserts data ... combo of acceptable and bad page splits are part of what's occurring. the job is significantly slower the day after we run our index defrag/maintenance scripts. another teammate is evaluating the quantity and characteristics of the data
You could use an two smallint columns:
create schema ponzi; /* a ponzi schema! Totally unnecessary */
create table foo (
from_year smallint not null,
to_year smallint not null,
check (from_year = to_year - 1 and from_year >= extract(year from current_date)),
unique (from_year, to_year)...
large MDB files have threat go get corrupt so it is advisable to use small files on server. But in the case of mdb file corruption you can use Access Fix Toolbox to get back your corrupt data. http://www.access.fixtoolbox.com/
Kindly refer to the page for instruction and download of the solution:...