Group: Forum Members
Posts: 2K,
Visits: 6.6K
|
I missed that there was any size limit on the number of records that a BO could handle (independent of hardware/network resources). I'll be interested to see if there is a limit.
Of course, network and hardware would likely be a limiting factor even if the BO can handle an unlimited number of records. 125 million records would require some serious memory and/or network connectivity (if you try to bring them all into the BO on a client machine....125 million records on an appropriately sized "modern" db server is very doable/done all the time). And then there is the issue of what in the world world would a user do with 125 million records available on their machine? If they browse a records every second, it would take something like 4 years to go through them (assuming no sleeping, eating, biology breaks at all).
If all 125 million records were all needed to perform some business logic, then I'd try to use SQL first. Or I'd try a server solution that sat very near the db (which might use a SF BO...if there aren't any limits). I know the SF guys use CLR sprocs to do heavy lifting like this, with great results (SQL 2005+).
Just some thoughts. I was intrigued by the post and thought I'd share them.
|