LinkedIn | FaceBook | Twitter
I've worked on several platforms, from Oracle and DB/2 to Sybase and SQL Server. Perhaps it's because SQL Server is so simple to set up, use and manage, but it seems that in this platform I see a lot of problems with people following best practices.
In fact, in some cases the DBA isn't even aware of the best practices for a particular item - like where and how you create a database. I suppose it's because of the ease of setup, people begin to treat the system as "totally automatic" and don't learn and follow the steps and settings that make the system stable, fast and recoverable. Then SQL Server is blamed for not being stable, fast or recoverable. It's like not putting gas in your car and then getting mad at the car when it won't start.
So I'll tag some of these blog entries as "Best Practices". I'll explain a little about a setting or practice, and point out a place for more information on the topic.
And the first best practice? To follow best practices! No, it isn't just learning what to do - it's actually doing it! If you want that stable, fast and recoverable system, you have to learn and follow the best way to do things. Don't worry - there aren't that many, and they aren't hard to do. A little time now, and you'll save a lot of heartache later.
PingBack from http://asp-net-hosting.simplynetdev.com/sql-server-best-practices-following-best-practices/