SQL 2000 db transactions/sec
SQL Server 2000, SQL Server database, SQL Server Database Transactions, SQL Server performance, SQL Server performance tuning, Windows Server 2003
What number of SQL 2000 database transactions/sec would be of concern on a system? Windows Server 2003, 4GB RAM, 2CPU (dual core).
Thanks for the guidance.
Software/Hardware used:
Software/Hardware used:
ASKED:
March 9, 2009 2:25 PM
UPDATED:
March 11, 2009 6:42 PM
RELATED QUESTIONS
- Truncating the transaction log for a SQL Server 2000 database
- Transact SQL stored executed from AS/400 CL program.
- Describing several performance monitoring counters
- Moving Distribution database from an instance to antother does increase performance ?
- Advantages of SQL Server 2005 over SQL Server 2000
Answer Wiki:
That all depends on how complex the transacations are and how well indexed the tables are.
If the tables aren't indexed correctly and the transactions are complex then a couple of hundred per second may be to many.
If the tables are well indexed and the transactions are small and simply then thousands could be fine.
It also depends on how much data the database has that the transactions need to access.
In other words I don't think there is enough information to give you a solid answer.
To see all answers submitted to the Answer Wiki: View Answer History.
Thanks for the information. I am seeing peaks about 200 transactions per sec but typically not much above that. Can you explain more about what a complex transaction means? The database in question captures QA data from circuit board manufacturing. It’s updating lot tracking information and what step the board is in the manufacturing process. I do not believe the volume of data is not large per transaction.
Note that this is also a single database server. There are no other databases on this system other than the default SQL 2000 databases. The databases reside on a Stonefly SAN. Are you familiar with that SAN or do you know of any issues of running SQL2000 on an iSCSI SAN?
200 tps is a decent amount of load. Complex transactions means transactions which have a lot of business logic in them, where simple transactions are just an insert, update, delete, or select with maybe some basic logic in there.
I don’t know that SAN specifically. In general there shouldn’t be any issues using an iSCSI SAN, but using iSCSI does present its own issues if you are having network issues.