SQL Gurus We are having a periodic problem with a heavily utilized SQL 2000 server. The server is scheduled to backup transaction logs on the news database every 4 hours throughout the day. The news database receives and processes about 8000 stories a day and it is hit continually throughout the day with selects against it for symbol news, keyword searches, and headline searches ordered by date. We've done a good job of tweaking indexes for maximum performance and the news services run quite well and they are very speedy. However, during the transaction log backup we are getting time outs on our odbc connection. It appears that the T-log backup is locking the table. T-log backups do not take a long time (about 30 seconds), but it does effectively take down any news oriented services for 30 seconds. This is NOT the behavior we had come to expect from our old SQL 7.0 database platform (although admittedly we had less activity).
My question is, is this expected behavior? Is there a way to prevent it? and does anyone have a really good SQL 2000 optimization checklist we could run through and see if we missed anything? Thanks! Mark A. Kruger, MCSE, CFG www.cfwebtools.com ..no more brochures! ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
