10 reasons why SQL Server 2008 is going to rock

Just like its predecessor, SQL Server 2008 is taking its sweet time to actually ship.  However, unlike its predecessor, it won't just be a "worthwhile upgrade".  It will kick ass.

Here are the top 10 reasons why.

10.  Plug-in model for SSMS.   SSMS 2005 also had a plug-in model, but it was not published, so the few developers that braved that environment were flying blind.  Apparently for 2008, the plug-in model will be published and a thousand add-ins will bloom. 

9.  Inline variable assignment.  I often wondered why, as a language, SQL languishes behind the times.  I mean, it has barely any modern syntactic sugar.  Well, in this version, they are at least scratching the the tip of the iceberg. 

Instead of:

DECLARE @myVar int   SET @myVar = 5

you can do it in one line:

DECLARE @myVar int = 5

Sweet.

8.  C like math syntax.  SET @i += 5.  Enough said.  They finally let a C# developer on the SQL team. 

7.  Auditing.  It's a 10 dollar word for storing changes to your data for later review, debugging or in response to regulatory laws.  It's a thankless and a mundane task and no one is ever excited by the prospect of writing triggers to handle it.  SQL Server 2008 introduces automatic auditing, so we can now check one thing off our to do list.

6.  Compression.  You may think that this feature is a waste of time, but it's not what it sounds like.  The release will offer row-level and page-level compression.  The compression mostly takes place on the metadata.  For instance, page compression will store common data for affected rows in a single place. 

The metadata storage for variable length fields is going to be completely crazy: they are pushing things into bits (instead of bytes).  For instance, length of the varchar will be stored in 3 bits. 

Anyway, I don't really care about space savings - storage is cheap.  What I do care about is that the feature promised (key word here "promises") to reduce I/O and RAM utilization, while increasing CPU utilization.  Every single performance problem I ever dealt with had to do with I/O overloading.  Will see how this plays out.  I am skeptical until I see some real world production benchmarks.

5.  Filtered Indexes.  This is another feature that sounds great - will have to see how it plays out.  Anyway, it allows you to create an index while specifying what rows are not to be in the index.  For example, index all rows where Status != null.  Theoretically, it'll get rid of all the dead weight in the index, allowing for faster queries. 

4.  Resource governor.  All I can say is FINALLY.  Sybase has had it since version 12 (that's last millennium, people).  Basically it allows the DBA to specify how much resources (e.g. CPU/RAM) each user is entitled to.  At the very least, it'll prevent people, with sparse SQL knowledge from shooting off a query with a Cartesian product and bringing down the box.

Actually Sybase is still ahead of MS on this feature.  Its ASE server allows you to prioritize one user over another - a feature that I found immensely useful.

3.  Plan freezing.  This is a solution to my personal pet peeve. Sometimes SQL Server decides to change its plan on you (in response to data changes, etc...).  If you've achieved your optimal query plan, now you can stick with it.  Yeah, I know, hints are evil, but there are situations when you want to take a hammer to SQL Server - well, this is the chill pill.

2.  Processing of delimited strings.   This is awesome and I could have used this feature...well, always.  Currently, we pass in delimited strings in the following manner:

exec sp_MySproc 'murphy,35;galen,31;samuels,27;colton,42'

Then the stored proc needs to parse the string into a usable form - a mindless task.

In 2008, Microsoft introduced Table Value Parameters (TVP). 

CREATE TYPE PeepsType AS TABLE (Name varchar(20), Age int)   DECLARE @myPeeps PeepsType   INSERT @myPeeps SELECT 'murphy', 35   INSERT @myPeeps SELECT 'galen', 31   INSERT @myPeeps SELECT 'samuels', 27   INSERT @myPeeps SELECT 'colton', 42    exec sp_MySproc2 @myPeeps 

And the sproc would look like this:

CREATE PROCEDURE sp_MySproc2(@myPeeps PeepsType READONLY) ...

The advantage here is that you can treat the Table Type as a regular table, use it in joins, etc.  Say goodbye to all those string parsing routines.

1. Intellisense in the SQL Server Management Studio (SSMS).  This has been previously possible in SQL Server 2000 and 2005 with use of 3rd party add-ins like SQL Prompt ($195).  But these tools are a horrible hack at best (e.g. they hook into the editor window and try to interpret what the application is doing). 

Built-in intellisense is huge - it means new people can easily learn the database schema as they go.

There are a ton of other great features - most of them small, but hugely useful.  There is a lot of polishing all over the place, like server resource monitoring right in SSMS, a la Vista. 

Ref.:http://angryhacker.com/blog/archive/2008/06/20/10-reasons-why-sql-server-2008-is-going-to-rock.aspx

 

How To Write An Interview Winning Resume

By John Sansom, 2012/07/19

Writing a resume that rocks is not an art. It just requires some planning and an understanding of what you want it to achieve for you.

Of course therein also lies the problem because many people are not exactly sure what they want their resume to do for them. This is why you will often see resumes that have listed every single technology feature a candidate has ever encountered, or why the hiring manager is reading a resume that is eight pages long and wondering when the pain of this monstrosity will all be over. The truth is the hiring manager never even reads the entire resume and instead simply moves immediately on to the next one without giving it a further thought.

Do you want your resume to be one that gets overlooked? Of course not!

I'm going to share with you exactly what you need to do in order to create an interview winning resume for a Database Administrator (DBA), Data Professional or any other darn profession you can think of for that matter. What prompted such an awesome display of generosity you ask? Well there is a story behind it (alluded to here) that you can ask me about next time we meet, but for now let's just pretend it's because I'm a super nice chap.

Regular readers will know that I'm a big fan of KISS. Not the awesome rock band but rather the principle of Keep It Simple Stupid! So for your reading pleasure I have compressed a wealth of winning resume writing knowledge into 4 simple rules. I know, impressive right.

In order to ensure that your resume gives you the best possible chance of securing your next interview it MUST be:

1. Readable
2. Relevant
3. Accurate
4. Valuable

Let's take a look at each rule in a little more detail to find out exactly what is required.

1. Readable

Your resume should be a pleasure to read. It should be an effortless experience for the reader, enabling them to immediately zone in on precisely the information they seek. The language you use should be concise and to the point. You've got a limited amount of space to use in order to sell yourself and you want to do so within two pages. That's right, your resume should be two pages maximum. Anything more and you are not being concise or relevant enough.

In summary some of the points you will want to consider are:

• Scannable – Is your resume easy on the eye? Can the reader easily locate information?
• Concise – Stay on point. Be specific and don't waffle.
• Incorporate bulleted lists – These will improve the structure of your content, making it scannable and easier to consume.
• Consider font choice - Keep it clear and professional. Stay away from creative fonts and color palettes.
• Two page limit - Don't squash your content. Be ruthless with what you include.

2. Relevant

Include only what is relevant to the "specific" role you are targeting your resume for. It can be tempting to list each and every skill that you may have, you might be putting your resume forward for a number of different opportunities but if the skills are not relevant then they won't demonstrate value(see 4.Value below) to the reader. The irony of a catch all resume is that it will actually get you nothing. It's demonstrably lazy. Don't do it!

In summary some of the points you will want to consider are:

• Be specific – Include ONLY the information pertinent to the role.
• Don't include references – You'll be asked for them if and when needed. Use the space for "valuable" content.
• Exclude personal interests – Your personality will come across/be promoted during the interview.

3. Accurate

The invention of the Spellchecker was a wonderful thing folks, so there really is no excuse for spelling mistakes or poor grammar. All good Data Professionals have excellent attention to detail, fail to get this one right and you're pretty much just demonstrating that you don't have what it takes.

In summary some of the points you will want to consider are:

• Spelling and Grammar – Check it, double check it, get someone else to proof read.
• Accuracy of facts and information – Use of correct product/technology names and versions.

4. Valuable

Why should I hire you? You know SQL Server clustering, so what? Why is that of use to me as a business owner? Demonstrate the business value you have delivered because of what you know or have done. Simply listing technology and skills is boring. Take your resume to the next level by clearly showing the reader how you delivered value using what you know. Be factual in your delivery and mind you don't take it to the other extreme or you'll end up coming across as boastful. The emphasis required on demonstrable financial value for a Sales Director is going to be a lot more than is needed for BI Developer. You need to find the right balance for your market.

In summary some of the points you will want to consider are:

• Expertise – Demonstrate your value through the results of your actions that were enabled by your skills.
• Key Achievements – Make a point of highlighting your big wins and achievements. Deployed an entire DR solution protecting assets worth £x million? Tell the reader.
• Demonstrable value – Revenue, costs savings, business awareness. What makes you an asset to have on staff?
• Passion – Show your love of technology(or chosen field) and for learning.

Keep It Simple

There you have it, four simple rules you should make sure your resume follows to give you the best possible chance of winning that next interview spot.

What do you think is important to creating an interview winning resume?

Best of luck with your job search!