Tag Info

New answers tagged

0

You should take a look at SciDB - a database designed for precisely this use case. It has as as its major driver Michael Stonebraker, a man who knows a lot about databases - it would be an exaggeration to say that he's been involved with more database systems than most people have had hot dinners, but not by much :-)! "including Ingres, Illustra, Cohera, ...


4

Your question reminds me of PostgreSQL. It has a feature called TOAST (The Outside Attribute Storage Technique). PostgreSQL features TOAST tables in the event the length of the row data is too small. I have discussed TOAST before in the DBA StackExchange May 01, 2012 : what is bigger than a longblob? Mar 21, 2012 : Are many NULL columns harmful in mysql ...


5

I would go for the same database, for the reasons you state in your question. If you're worried about performance or growth, create a new "logging" filegroup and put the logging table(s) on that. If things grow out of hand in the future, you can move the .ndf (the physical file that contains the new filegroup) to a different physical drive. Even if you ...



Top 50 recent answers are included