Can Your Database Handle the Stress?
Just a Day Left for Current Early Bird Rates
The SSWUG.ORG Virtual Conference - all 74+ sessions of it! - rates will be going up in the next day or two. We're holding them off just a bit for last minute registrations at the current rates. Make sure you register today - and here's a VIP link that you can use to save additional money off the early bird rate:
>> http://www.vconferenceonline.com/autovip.asp?vip=VIPNL09031
Featured Article(s)
New Features in Silverlight 4 - Part 1
Silverlight (formerly known as Windows Presentation Foundation Everywhere) is a browser plug-in that can be used to enhance the look and feel of web based applications designed on top of the managed environment of the CLR. Silverlight 4.0 is a new version of Silverlight that runs on top of .NET Framework 4.0 and adds lot of new and exciting features to the earlier versions of Silverlight. This is a first part in the series of two articles that takes a quick glance at the new and exciting features in Silverlight 4.
Featured White Paper(s)
Developing Something for Nothing with SQL Server: A Closer Look at SQL Server Express and How it Can Work for You
In this new Quest Software technical brief, learn about SQL Server Express – Microsoft’s free version of SQL Server – and how... (read more)
Can Your Database Handle the Stress?
Stress testing is one of the last things we tend to implement when developing a database. There are lots of reasons I can think of without really trying:
- It's hard to stress test when you don't have a lot of data already in the database.
- It's difficult to predict what kinds of loads will really occur.
- It's difficult and/or expensive to build a hardware and software environment providing expected results from your production systems.
- It takes time/resources/$ to develop stress tests.
- It's just not fun and feels like the time isn't worth the risk.
The cost of not stress testing came home to me recently when a client added the proverbial straw, breaking the camel's back. They were using a view that was on the cusp of not working. It had many tables, a few scalar functions, and a lot (I mean a LOT) of case statements with multiple branches. The view was already on our radar to be re-factored.
Before we could get to it, another requirement came that was implemented with one additional case statement. We made the change and unit tested with great success. So, the change was pushed into production, where things quickly choked and died.
Query performance times went from sub second to a minute or more; just adding that one last case statement.
Many of us have experienced this kind of scenario. So, I'm looking for experiences and solutions from you. Vendors that have tools to help with this kind of problem are invited to reply as well. All comers are welcome. Send your responses to btaylor@sswug.org and I'll be glad to post them in future newsletters. Feel free to send input for other reasons you have not been able to implement stress testing as well.
Cheers,
Ben
SSWUG.org Free Expo Event Friday, September 24, 2010 9:00 a.m. PT
This free expo will focus on SQL Server Performance Monitoring, Tuning & Troubleshooting. Working with SQL Server to provide for excellent performance means understanding your options. This expo will focus on items you’ll want to know for monitoring your SQL Servers, then what you can do with that information to have systems that work well.
Register here.
|
9/3/2010
|
How to Grow a DBA
Featured Article(s)
Building Simple Reports with Reporting Services (Part 1 of 5)
We're going to show how to create both simple reports and reports with variables. We will discuss how to manage those reports once you’ve created them including how to secure your reports. And finally we will discuss how to allow your users to access those reports. Throughout the session we will be doing demos of nearly every feature of Reporting Services.
How To Grow a DBA
Thank you for the large response to my editorial on How To Grow a DBA on 8/24. In it I shared then the story of a Business Analyst who wanted to become a DBA and was looking for insight how to make the transition.
My in box filled rapidly with responses, so don't be hurt if your's isn't presented here.
One of the ways many of our readers were able to make the switch was by becoming deeply interested in projects requiring their current skills allowing them to work closely with the technical implementation.
Adam writes:
I was an MIS Analyst (build/run reports) with ... and we needed a data mart. The report data was stored in Access, but that was falling apart so my manager decided to use SQL Server 2000. I had to figure out how to use SQL Server through trial and error (lots of errors). The company then built a large data warehouse and I was very involved with that. It started me down the road of being a DBD/DBA – mostly in SQL Server, but I’ve dabbled in MySQL, DB2, and Oracle. Today, 10 years later, I do DBD and DBA work for a large non-profit. I never meant to do this type of work, but I’m happy to be an accidental DBA.
Steve started by taking the point for implementing a new technology:
I became a DBA when my employer decided to use DB2 on MVS. This would have been in '86 or '87; DB2 version 1.2. I was asked if I wanted to work on the first application that would use DB2 or if I would be interested in administering DB2. That was an easy decision; I wanted to know it intimately rather than just use it.
You mention becoming an intern or a DBA assistant. No, since I was the ONLY one I had to learn on my own. Well, I did take a few classes. And the user groups were a big help when I could get to them. They were 100 miles South or 200 hundred miles North.
Since then I've worked with lots of RDBMSes on several different platforms, but my favorite is still Big DB2.
A DBA has to know so much - software install, tuning at the system level and the appl level, data design, application design, the utilities and knowing when they are needed, recovery, help EVERYBODY with EVERYTHING including JCL and COBOL and Assembler (because the program accesses DB2), DBA needs to know communications between boxes and OSes, gotta have a good logical programmer mind, the progamming staff will expect the DBA to know the programmer's application better than the programmer does, and on and on and on. Did I even mention SQL? a DBA needs to know how to code SQL and do it well.
It can be rewarding, but it is a challenge. Someone should only pursue being a DBA if they love the challenge and are willing to WORK and not just "Google it."
I'll share some more insights next week. In the mean time, if you have a topic you'd like to see addressed feel free to drop a note or comment to btaylor@sswug.org.
Cheers,
Ben
Featured Script
dba3_NorthWind_0050_Materialized_View_Invoices_Article
View it now! - Part II: Banishing view timeouts by implementing user "materialized views"... (read more)
|
9/2/2010
|
Bit Mapping Rewind
Featured Article(s)
SQL Server 2008 Temporary Tables Optimization Tips
In this article, you can find some tips to use SQL Server 2008 temporary tables.
Bit Mapping Rewind
So I've been playing with Bit Maps and had a few things to share as a follow up of the editorial of 8/20/2010.
Like most ideas, they aren't new. Just new application of things we did years ago.
Ed writes:
Just a small cavil - In the last paragraph of the article "And a Little Bit More" of the 8/20/10 SSWUG newsletter, you said "...my intention is to wet your appetite...". I'm sure you hope to whet (sharpen it or give it an edge) our appetite rather than pour cold water over us.
But thanks for the article. Using the bit mask is an old IMS trick to save space but still be searchable back when IMS didn't do bits. Good idea and very well written.
Well, Ed, I appreciate the editing. Grammar has always been my weakest skill (besides surfing).
So, while playing with the idea I had a customer with a table containing 200+ bit columns that were truly unique. The table only had 140k rows. No matter what I did it ended up performing a table scan because of all the comparisons being performed. I was able to reduce the 200+ columns into four BIGINT columns.
Since the optimizer was performing a table scan I created a clustered index on the few non BIT columns, for which user parameters were supplied, reducing the number of comparisons marginally. Then I converted each of the BIT input Parameters into 4 BIT MAP BIGINT Variables. Short story, my query time dropped from 2+ seconds to 156 ms. Even though it had to perform a bitwise AND on every row that was scanned, and convert the input parameters into 4 comparison variables..
I guess thats enough on bits. I just wanted to whet your appetite :-) and encourage you to try them when you have a problem that really needs them. The save space, and can increase query performance when BIT columns are needed.
Keep your comments and critiques coming to btaylor@sswug.org. We're always open to things you'd like us to cover as well.
Cheers,
Ben
|
9/1/2010
|
Is There a Shortage of SQL Server Experts?
Last Day to Register for the SSIS class...
12 sessions a month of learning, lots of help from SQL Server MVP Eric Johnson, all about SSIS. You can't go wrong!
Check it out here to get more information - class starts Sept 1!
Is There a Shortage of SQL Server Experts?
I came across this question in a news group thread and started thinking how I might respond. Then I started asking myself, "am I an expert in SQL Server, or any part of it?"
Frankly, I'm good, and can figure out most things. I've been working with Relational databases since 1983, and different brands of SQL since 1985. Still, I don't consider myself an expert. It seems like every week I find a new facet or feature that I didn't know. Or I find something I used to know was a fact about SQL Server that is no longer true.
With the growing number of features that are a part of SQL Server I'm just happy to know they exist. For example, I know that SQL Server supports integrating of File Streams into a transaction. I have not had an application that needed that feature, so my knowledge has no experience. SSIS, SSRS, SSAS are all products in their own right, and since bundled with SQL Server tend to be considered a part of that expertise.
I'm thinking we really need more SQL MVPs; people who know generic SQL Syntax; people who know engine specific strategies; people who know different operating systems hosting an SQL engine which has to integrate in some fashion.
MVPs are not necessarily an expert in all things SQL. Instead they share with the SQL community their areas of knowledge, and are willing to help others solve real world problems. In my opinion these are the people who are real champions. MVPs tend to take us from our current point of knowledge and move us forward with resources or instructions for better work. They are contrasted with the expert intentionally making us feel stupid for not asking the right question, or asking the right question with a solution that differs from their experience.
Let's hear it for the MVP.
So, what does it really take to really be an SQL Server expert? Are there people you consider to be experts in SQL Server? Do you look for experts? What is the true value of an expert? Send your thoughts our comments to btaylor@sswug.org.
Cheers,
Ben
Featured Script
dfrag SQL
This routine uses a cursor to do some defragmentation on your db tables... (read more)
SSWUG.org Free Expo Event Friday, September 24, 2010 9:00 a.m. PT
This free expo will be all about SQL Server Performance Monitoring, Tuning & Troubleshooting. Working with SQL Server to provide for excellent performance means understanding your options. This expo will focus on items you’ll want to know for monitoring your SQL Servers, then what you can do with that information to have systems that work well.
Register here.
|
8/31/2010
|
Are You Working with Smaller Teams?
New selecTViews Video Posted
Today Ben Miller joins me on selecTViews. We talked about how companies work with developer and DBA teams, what works, what doesn't and a lot more.
[Check out the show here]
Free Webcast Available Now:
Get Your Implementation Organized
When it comes to SharePoint environments, if you don't plan ahead, your environment can quickly become a disorganized mess of IIS, SQL & SharePoint components. Suddenly you don't know what web application maps to what application pool in IIS, or even worse, you don't know what service accounts perform what functions! This session will cover strategies and provide recommendations on ways that SharePoint administrators can reign in their farm and make sure that no matter who is managing it, everyone is on the same page. Organization is key and this session will help get you one step closer to organization nirvana.
Presented by: Christopher Regan
> Register Now and watch now.
Are You Working with Smaller Teams?
Send in your experiences here.
Donald writes "Our teams for projects are smaller than in the past, for the simple fact that our staff like with most companies has decreased over the last few years – thought we are in the process of hiring for two positions. (which is harder than we thought it would be in this economy)
We have seen a positive impact to the smaller teams – they tend to work faster, have better communication and tend to work together better than the larger teams. We also build into any project documentation, training, post go live support, follow up and disaster recovery. The quality of our projects has in fact in most cases improved and we have seen fewer issues after go live than we have in the past.
Our Management has even noted that they were surprised to see the amount of time spent on projects decrease, the number of them being completed increase and the quality go up. I think a lot of this is due to the team really working together, getting to know each other and all pulling together to make it happen.
Some of our partner companies are having the issue you noted. In most cases we have found that it not just a staffing issue – but a mindset issue with the partner. They feel they need to get a project done quickly – and they tend to cut out steps in doing so – and then they do jump right to the next project – leaving you without developers that know the product to fix any issues that come up. In many cases it seems they just want to get something out the door so they can bill for it – and then worry about the quality later.
I expect that even as our staff grows again, we will see the teams remain small, allowing them to be more agile. Sometimes, smaller is better"
Featured Article(s)
Step By Step DB2 9.X install on AIX Manual Method - Part 2
Step By Step DB2 9.X install on AIX Manual Method - Part 2
Featured White Paper(s)
VIDEO WHITEPAPER - How to Avoid Downtime - VIDEO WHITEPAPER
In this Experts & Insights video, we take a close-up look at the data protection challenges and solutions surrounding downtim... (read more)
|
8/30/2010
|
|
