When to Use an ImageNow Custom Property

By: | Tags: , , , , | Comments: 0

One of the most important times to use custom properties instead of index values in ImageNow/Perceptive Content is when you’re working with dates. Using a custom property allows searching by data ranges and other functionality not available with index value searches. Remember: index values are strings and nothing more.

Performance must also be considered. Adding too many custom properties will severely impact performance, as the chart below illustrates.

Database Size Growth Chart
Reference: 1 Document requires 2.336KB of database storage
Each Custom Property adds: 0.5KB of storage

DB Growth w/ CP (in KB) Space Required for
Base Documents
w/ 1 Cust Prop w/ 5 Cust Prop w/ 10 CP w/ 20 CP

1 document

2.34

2.84

16.52

30.70

59.06

100,000 documents

233,600

283,600

483,600

733,600

1,233,600

250,000 documents

584,000

709,000

1,209,000

1,834,000

3,084,000

500,000 documents

1,168,000

1,418,000

2,418,000

3,668,000

6,168,000

1,000,000 documents

2,336,000

2,836,000

4,836,000

7,336,000

12,336,000

Broken Down in MB

100,000 documents

228

277

472

716

1,205

250,000 documents

570

692

1,181

1,791

3,012

500,000 documents

1,141

1,385

2,361

3,582

6,023

1,000,000 documents

2,281

2,770

4,723

7,164

12,047

Broken Down in GB

100,000 documents

0.22

0.27

0.46

0.70

1.18

250,000 documents

0.56

0.68

1.15

1.75

2.94

500,000 documents

1.11

1.35

2.31

3.50

5.88

1,000,000 documents

2.23

2.70

4.61

7.00

11.76

Also note that Oracle db’s will use more storage than a MSSQL database due to the function based indexes (use 1.75 as a rough multiplier).

You must be logged in to post a comment.