I was doing my morning reading and came across this nugget from Jose Barreto:
Maintaining your MOSS 2007 SQL Databases
Mr. Barreto's point is that while Microsoft Office Sharepoint Server (MOSS ) 2007 will do the database creation for you when installed, there still needs to be database maintenance performed. In the case of MOSS 2007, he says there may be as many as 8 databases if all the features are installed. Mr. Barreto's blog walks a user through the simple steps of seeing what databases are present, seeing what recovery modes they're using, and how to setup maintenanace plans for these databases. Even with all of that said, he still concludes with:
Keep in mind that the best option of all is to have a real Database Administrator around and design the best maintenance and backup scheme for your specific scenario, which might include using the full recovery model and a combination of regularly scheduled full and incremental backups.
Organizations may be lulled into thinking that since the setup does the work of getting the databases established, the database maintenance is also taken care of. This just doesn't make a whole lot of sense. That's like saying since the car dealership sold the car with everything running, it's up to the dealership to keep the car maintained. I don't know about you, but I haven't bought from a dealership that comes out and keeps my car in top form without me noticing about it and without me being charged a single dime. Yet what we won't expect from our cars we expect from our databases. Operationally it's a huge risk to take. And as Andy pointed out, enterprises feel the effects of not having database professional design databases, though they may not even realize it.
This is true regardless of database platform and version. SQL Server 2005 may be built to be more reliable than and fix bugs found in SQL Server 2000, but that doesn't mean it eliminates maintenance all together. MySQL 5.0 may be built to be more reliable than and fix bugs found in MySQL 4.0, but you still need to maintain it. We can say this for any enterprise database platform: DB2, MySQL, Oracle, SQL Server, or Sybase (to namea few). Even a Microsoft Access jet database needs a Compact & Repair every so often. And all of them, while trying to improve on performance, can never completely counteract the effects of poor database design.
Technorati Tags: DATABASE | SQL Server | Microsoft SQL Server | SQL Server 2000 | SQL Server 2005 | MySQL