Hi, sorry I am still fairly new, i get the size issue, and I am planning on archiving older information on a yearly basis anyway, although i have never done it so i am unsure how it will work, there will be millions of records in the DB, but if I am filtering
the searches anyway using where Active there would there still be substancial benefits to putting the history in a different database or seprate tables?
(it might be more viable, I am still building but I have got so far going back and changing it all would be a pain....)
Do you have and examples or tutorials on triggers, they look interesting but the docs are meaningless to me unless i can see working examples.
EnenDaveyBoy
Participant
1465 Points
1146 Posts
Re: Entity Framwork / Navigation Property / SQL issue
Jul 13, 2011 10:16 AM|LINK
Hi, sorry I am still fairly new, i get the size issue, and I am planning on archiving older information on a yearly basis anyway, although i have never done it so i am unsure how it will work, there will be millions of records in the DB, but if I am filtering the searches anyway using where Active there would there still be substancial benefits to putting the history in a different database or seprate tables?
(it might be more viable, I am still building but I have got so far going back and changing it all would be a pain....)
Do you have and examples or tutorials on triggers, they look interesting but the docs are meaningless to me unless i can see working examples.