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!
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.