Archive for February 11, 2010

Have you Ever Noticed…

Posted: February 11, 2010 in Uncategorized

*Warning not just SQL*

 

Example 1

I just bought a new truck, see I was paying for my charger to sit in the garage and was driving my older truck, my older truck would not have made the months of the 150 miles I have to drive to work each day. Well here is the point. My sales guy and his manager were doing everything they could to sell me this truck, and they made me a great deal. There were a number of things that they were going to do and it was agreed upon before the sale. It was even on the “We Owe” document, but when it came down to it they kept my truck 21 days and I had to pay for the last part. The reason “We are not making any money on this because of the repairs we have done”. Is this my fault? The sales guy, the manager, and the service manager said they would fix what is broken, it says it on the contract.

Example 2

A number of years ago I bought some software that I was told would monitor my SQL Server. You would know this company name and they do make a good product but the other product was an unknown. During the discussion the sales person let us know that we could return the software if we did not like it. So we bought it. It took us 6 weeks to get the software back and we replaced it with SQL Sentry.

I guess my question is why don’t people just do the right thing? Isn’t this world under enough stress without this crap. I had to deal with a Vendor that I told they were out of my price range for a product. Yet they wanted to give a presentation, then they sent me a quote, the quote was twice what I could spend. They ask for the reason that I turned them down and when I told them they were not listening to my requirements set out to me by budget. So they said they would cut the price. A hour later the next quote was only 25% higher than what I told them I could pay.

End Result… Why do people push you until you have to act like a jerk? I can tell you don’t by a Dodge in North Colorado Springs, Stay away from San Francisco software company’s performance software, and listen to your customers. If you want them to stay customers.

SQL Server Indexing Workshop

Posted: February 11, 2010 in Uncategorized

 

SSWUG is hosting –

Last Day To Register for Kalen’s First-Ever Virtual Workshop
This week’s virtual workshop is going to be very cool – Kalen Delaney will be teaching about Indexes – and it’s going to be amazing!  Kalen is well known for her in-depth approach to teaching workshops, classes, pre-conference sessions and so much more.  We’re really jazzed about bringing you more than *4 hours* of detailed information about things you need to know about Indexes and SQL Server.  Learn about key aspects of indexes and, perhaps more importantly, how to apply that knowledge to get the best possible performance from your systems.  Take a look here at the virtual workshop site – but don’t delay – the workshop is Friday, so be sure to register today.   We’ll even be giving away a copy of her book to one lucky workshop attendee!

>> [Visit the workshop site]
>> [Register for the virtual workshop]

Reality-Based Tuning
Earlier this week I mentioned that it can be really helpful to review how your applications are really used, then compare that to your designs and how you have SQL Server configured. 

I wanted to touch on a few more things that can be impacted by the reality-based reviews of your systems.  Some of these may apply, some may not, but they’re probably worth considering as you look over your systems and how they’re being used by your end-users.

– Watch for too many joins – if you’re doing extensive reporting and have built a number of reports, and the underlying views and such for those reports, you may want to look into a data warehouse/data mart for those applications.  You can denormalize (EEK!) your tables a bit to support the queries your users need to answer and save a lot of work from SQL Server.  

– Conversely, watch for too many indexes on OLTP tables.  Many times we add indexes on tables to support queries.  Makes sense, sure.  It can help performance on queries, but it can also hurt performance on insert/update operations.  Too many indexes can force SQL Server to work harder to insert and update information in your systems.  It’s a fine line you need to walk when considering which indexes, and when there may be too many… 

– Today’s last quick suggestion is to consider using the right tools on the front-end in support of your users.  If you really do have a lot of query work being done, consider using a tool that can pull information, then work with it locally.  A good example of this is the new PowerPivot tool.  Pull information to tools that let you query and work with information, try to work away from the database to do the reporting.