Morning Lester, > My own data from sites is slowly growing and has 10+ years of history much of > which will never be read again, but needs to be available, so I've started > moving the historic stuff to a second database which is read only except for > an > 'archive' cycle perhaps once every 6 months. This can then take advantage of > the > read only mode and in my case a USB stick works as the off-line storage. That > feels like the right way to develop things, but which might benefit from > better > 'cross database' facilities? With bulk data static on an SSD array, while the > active stuff is in memory?
Sounds a bit like you are thinking of something like Oracle Tablespaces. These are used to separate distinct sets of tables (and/or indices) according to the needs of the application(s) running on that particular database. Your setup sounds like it would benefit from a couple - active and archive. You'd create the files for the active tables on read-write media while the archive stuff would be created as read-write, but run off the SSDs in read-only mode. When creating a table, you simply add "tablespace <whatever>" to the create table statement, and it will be created in the correct place. I have no idea how easy/hard/sane it would be to add this sort of thing to Firebird of course! ;-) Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: Thorpe House 61 Richardshaw Lane Pudsey West Yorkshire United Kingdom LS28 7EL Company Number: 05132767
