> > Good ideas on how to look at performance and what to consider. > > > https://www.mssqltips.com/sqlservertip/2453/sql-server-performance-tuning-for-each-layer-of-an-application/
Sorry, have to disagree here... That article merely lists some random performance counters that cover only a tiny fraction of performance related issues and do not help solving the issue. A few examples: - Weekly rebuilds of the index will kill your transaction log if you do not have a backup plan - Whenever tables have mixed read/write access locking becomes a lot more important. - SQL server can only handle a limited amount of transactions per second, because every COMMIT causes physical disk activity. That counter is completely missing. -- Christof --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cal4qjhgg-ko7aukdaju4rlkmd59ue-9lpkwnn+rjjl2npp_...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
