 |
XML feed failed
|
Sponsored Listings
|
|
|
|
|
|
Comments
OMG!
by [GUEST](193.222.136.x) at 2011-07-27 00:24:44
Please withdraw or expand. Worded this way it's not good advice.
Good, but needs more depth
by [GUEST](69.176.78.x) at 2011-07-26 13:50:52
I think what the other comments are trying to say is that the optimization tips you gave are pretty deep to cover in a brief article. There are a lot of things to consider when using software tools, optimizing indexes and planning hardware. In fact, thick books have been written about each of the topics. You may want to expand on each of the sections, or provide links to locations where people can go to get additional information. For example, "Use performance monitoring tools" is a great suggestion, but it doesn't help someone actually do it. If you provided links to information about SQL Profiler, Microsoft's Performance Monitor, SQL Server Data Collector, examples on how to build a baseline, or other tools and best practices, it would give people a place to go. Alternatively, you could go deep in just a single topic, maybe focusing the entire article on performance with clustered and non-clustered indexes, and how when utilized appropriately they are an incredible optimization tool. I'm afraid that because you tried to do both - have a broad scope and specific detail - it has created just enough information to be dangerous, and someone that came here hoping to actually perform some optimization may make decisions without fully understanding the consequences.
Very very concerning . . .
by [GUEST](62.189.140.x) at 2011-07-26 05:44:35
that people may read this and take it to be correct
Professional?
by [GUEST](188.221.9.x) at 2011-07-26 05:34:36
The only good advice here is "You should use a professional to take care of SQL server.". The quality of the rest of teh advice suggests that following it would not be using a professional.
Hmmm
by [GUEST](201.42.139.x) at 2011-07-26 05:28:01
"Do not use indexes on tables that you update often."
Do you really consider not using any indexes at all useful, not even a primary key?
Where's the -5 rating?
by [GUEST](208.84.104.x) at 2011-07-26 04:41:42
Completely useless advice and wrong in so many ways.
Very Poor Advice
by [GUEST](96.252.78.x) at 2011-07-26 04:32:50
I'd be extremely cautious about implementing this advice. For example, "use clustered indexes with caution..." No, the clustered index is a fundamental part of how SQL Server stores data. It should be the foundation for the data structure design and for the queries run against it. Another, "Don't use indexes on tables you update often." Well, assuming an update, unless you're updating all data in the table, you'll have a WHERE clause. If you don't have indexes that support that WHERE clause, your performance will be horrible. There's more that's wrong here. Please, don't follow this advice.
|
Post a comment
|
|
|
|
Sponsored Listings
|
- Sql Server Optimization
- Sql Certification
- Sql Server
- Sql Training
- Online Databases
- Database Administration
- Server Hardware
|
| | |
|
|
