Hi, yesterday I found out that setting a database on auto growth is not a very good thing.
Are there other basic 'bad' practices (or best practices) when having SQL Server databases in production?
thx, Lieven Cardoen
+8
A:
Do you have data and logs on separate devices. Is tempdb a reasonable size? Do you have disaster recovery plan? The first time you have to recover a database is not the time to start reading up on how to do it!
Are you running the default maintenance plan (DBCC, update statistics and all that stuff)? Do you know what it all does and do you monitor it for any issues?
Do you have some performance metrics on disk I/O, memory, cpu. Maybe some queries you can monitor on a regular basis and look for performance degradation.
With a new application and database, all your queries will be fast for awhile, but as your database grows, performance problems may sneak up on you if you aren't proactive.
MikeW
2009-03-05 08:44:14
Any good links on this? thx
Lieven Cardoen
2009-03-05 09:53:38
There are, will have to hunt them down. If you don't know a lot about the above, you probably should get a SQL Server book - there are a few good ones on Tuning that cover configuration and metrics.
MikeW
2009-03-05 10:03:53
Thx, will check those.
Lieven Cardoen
2009-03-05 10:08:05
+3
A:
stop the sql server from using all available memory... on a box with 4gb of ram, i'd limit it to 3gb, ensuring 1gb is left for the os.
GordonB
2009-03-05 08:44:48
+1
A:
My personal favourite:
Do you have a backup plan?
I've seen too many databases with the transaction logs filling up the disk...
If you're getting seriouw with SQL take a look at SqlServerCentral.com. They have many good articles on everything sql related.
thijs
2009-03-05 10:11:29