I was recently brought in to evaluate slow performance of an ERP solution. They are running SQL Server 2008 R2. Their database size is about 90GB and the server has 16GB RAM. It was immediately apparent that their server is grossly underpowered and the prime suspect is the drive array. No one knows exactly what drives are in there and how they are configured. Plus one of the lights on the array is blinking red. Given this, we have them ordering a new server that is built to the specs of the ERP solution. My question right now is what can I do with the old server to increase its speed while we wait for the new server? They just rebooted the server on Friday and by Monday morning the tempdb has grown to over 3GB and I cannot spot any process they perform that would require such growth. We will be runninging DBCC CHECKDB and CHECKCATALOG tonight and perhaps REINDEX. What else would be the top tuning procedures for SQL I should look at to get this server to be marginally acceptable? That blinking red light is most concerning but there is nothing I can do about that.
In this article, we will show how to detach and attach a database and then show how to repair a corrupt database and attach it, If it has some errors. We will show how to detach and attach using SSMS or using T-SQL sentences.
SQL Database Recovery Software repairs the MDF & NDF Files, corrupted due to hardware related issues or software related errors. Provides preview of recovered database objects and allows saving in either MSSQL, CSV, HTML or XLS format. Ensures recov…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.