If youre happy with the execution plan and just want NHibernate to
accept the long running query, you can increase the command timeout
("command_timeout") in NHibernate.Regards Carsten Hess On Apr 5, 10:14 am, Gustavo Ringel <[email protected]> wrote: > Maybe you can denormalize and perform some calculations before writing to > the archive tables so you have a report oriented model and minimize joins, > etc... > > I do writes to the report database asynchronously so i have the time to > prepare the data for reporting and avoid doing calculations and joins when > reporting... > > When i started with this i thought i was crazy but then i have read here: > > http://martinfowler.com/bliki/ReportingDatabase.html > > and something from Greg Young that i cannot find now with the same ideas i > used. > > I did something much more simpler for sure but the idea can be taken from > there... > > Gustavo. > > > > On Sun, Apr 5, 2009 at 11:03 AM, Dotan N. <[email protected]> wrote: > > hey all, > > whats the current solution for having archive tables and sometimes > > performing queries on them, right now i'm getting timeouts like crazy (im > > talking > 1M records, and not cutting edge servers). i have indexes > > whereever possible and the most taxing goes on index seeks (i looked at > > execution plan) > > > any ideas? > > > thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
