Just moved from wrong forum i paste here my question:
I just got a new client recently migrated from SQL Server 2000 to SQL Server 2005 due to vendor application limitation to new releases. Vendor application is compatible only max to SQL Server 2005. I found that the database never got a maintenance plan: it's about 14 years old, always up and, fortunately, always backed up (daily full backup, 4 hour differential and 10 minutes transaction log backup).
At first glance DB is split in 4
.mdf files (10Gb, 30Gb, 2Gb, 2Gb) and one
.ldf file of 35Gb.
.ldf is quite big because transactions log are max 100 mb. For what office folks say during those years there were 2 - 3 big deletion, but they don't know anything else. Server is a bit old (IBM x346, 8Gb Ram and only 70gb of free hd space), running W2003 R2 32bit with /pae and SQL Server 2005 with AWE.
At first glance index fragmentation is HUGE.
What are the best practices to start 'revive' :-) this situation ?