title: Search for information on building large enterprise systems
body: <p>How do you organize DB layer, business logic and cross-platform API of your information management system, if uploading and processing 500000 data records in one session is a normal operation (C# .NET 3.5 + MS SQL 2005)?</p>
  
  <p>I’m specifically interested in production-proven paging patterns that behave well with the concurrency, scalability and reliability.</p>
  
  <p>Does anybody have any ideas, in what direction to dig?</p>
  
  <ul>
  <li>Open Source Projects (don’t care about the language or platform, as long as it is not Ook)</li>
  <li>books</li>
  <li>articles</li>
  <li>Google keywords</li>
  <li>forums or newsgroups</li>
  </ul>
  
  <p>Any help would greatly appreciated!</p>
  
  <p><strong>Update:</strong></p>
  
  <ul>
  <li>simple paging (i.e.: rownumber in
  SQL 2005) does not work, since there
  are a lot of <strong>concurrent</strong> changes
  to the database. Item, that is deleted or inserted between the page requests, automatically makes current page index invalid.</li>
  </ul>