You would create these the same way you would the Code Snippets. When you are in SSMS (SQL Server management Studio) and open a New Query window, you can simply right-click in that window and click on Surround With… (You can also type Crtl+K, Ctrl+S). The third way is to click Edit on the main menu, chose IntelliSense > Surround With…

Once you click Surround With… it will display 3 different choices. They are the Begin Statement, the If Statement or the While Statement.

Once you click on one, it will write the basic T-SQL code for you. All you have to do is fill in the Condition and what you wish to execute during that condition.

Is this a huge time saver? Not really, but for people new to T-SQL coding, it will set them up with the basic format.

So how do we do this? In this case, you will need to open the Code Snippets Manager. To do this, go to Tools -> Code Snippets Manager… or Ctrl+K, Ctrl+B.

This will open up all of the Code Snippets that come canned in SQL 2012. What is important to recognize is that all of these code snippets are actually xml files. In this example, I am going to create a custom code snippet for a stored procedure with a comment block at the top. The easiest way is to just copy the canned ‘Create Procedure  Basic Template’ and modify it. From the image below, you can see I identified where the xml files currently reside.

I created a folder called Custom_Snippets on my C: Drive, copied the xml file and renamed it ‘SP_wCmntBlk.snippet’.Once that xml file was copied to my new folder, I can open it with Visual Studio or notepad update it to look like this.

Once I finish updating the xml code, I save it. Then, back in the Code Snippets Manager, I click Add, drill down to the folder I created called Custom_Snippets and click Select Folder. This folder will now show up in the Code Snippets Manager. In fact, any .snippet file you place in the folder will now automatically be visable.

Now if I open up SSMS, Open a New Query, right-click in the query editor and click Insert Snippet, I will see my Custom Snippet folder and can select the snippet I just created.

You don’t need to be an expert with xml to do this as I just showed you. It is rather simple and can be very useful.  Try it our and let me know what your thoughts are!

When you are in SSMS (SQL Server management Studio) and open a New Query window, you can simply right-click in that window and click on Insert Snippet… (You can also type Crtl+K, Ctrl+X)

This will display server different object in which you can create a generic code snippet for. In this case, we will look at creating a basic Stored Procedure shell. Once you choose the Create a single stored procedure option, generic code is created for you to use.

All you have to do is fill in the highlighted sections.

The same is true for all of the other objects listed in the snippets. You might already know the syntax to all of this, most of us DBA’s do, but this is also a no brainer and time saver in the sense that it is very easy to click n’ create. This can help new developers and old developers alike.

Take a minute and check it out.

Within the SQL 2012 SSMS window, click on Tools -> Options…

Once the Options screen opens up, you will navigate down to find the Display settings.

Text Editor -> Transact-SQL -> General 

Once you get here, enable the Line numbers check box and click ok.

Now when you open a new query in SSMS, you will see the line numbers! Super easy!

You can sign up here.
See the line up of speakers here.

Make sure to keep your 4PM session open for myself and Dilip Nayak (t) called Get TurnedOn with AlwaysOn. We will be presenting on SQL 2012 AlwaysON (HA\DR). This is going to be a great introduction session for anyone interested in learning about AlwaysOn, the features associated with it and how to set it up.

If you have never been to a SQL Saturday, you are really missing out on some top notch training as well as a great opportunity to network with others with the same interests.

You got plans on July 28, 2012? Hopefully your answer is ‘No’. The Sacramento SQL Server User Group is going to be putting on a great day of FREE SQL learning. In case you haven’t seen the speaker list, we have already gotten submissions from some great folks both local and national on topics from Database Administration to Business Intelligence and SQL 2012. Maybe you have heard of some of them!

We have a really great planning team who is working their tails off to try and put together a truly outstanding event. We will be having the event at a very lush local venue that is close to downtown Sacramento and Cisco will be hosting an after party at a restaurant on the Sacramento River (more details to come). Check out the SQL Sat 144 website to sign up now and get more information. If you are interested in presenting, we would love to hear from you! We are always looking for people to speak at out local user group meetings as well as events like this.

Can’t wait to see everyone on July 28th!

Why is it important some might ask, well, let me explain. Almost all production SQL environments have some sort of back up strategy which includes some combination of full backups, differential backups and/or Transactional log backups. For instance, a full backup is taken on a database every weekend. This creates a starting reference point for a restore.  After the full backup, differential backups are taken nightly with additional transaction log (TLog) backups taken at specified intervals throughout the day to create what is called a log chain. All of these differential and TLog backups are tied directly to the preceding full backup. A Log Sequence Number (LSN) is created to keep all the backups in order. When a restore is required, the full backup must be restored with all the proper differential and TLog backups. If one is missing, the restore will fail. The important thing here is that after a full backup, all of the differential and TLog backups following it are tied directly to that Full backup.

So, assuming we are all very organized and keep all of our backups automated and documented properly, we should be able to perform a point in time restore without issue. But what happens if one of your co-workers takes an AdHoc full backup of a database to restore to a development environment without telling anyone. Later that day you need to restore the database to a point in time after the AdHoc back up was taken by your co-worker? The restore will fail since the Log Chain was broke by the AdHoc full backup and the LSN’s are no longer in sync with the original full backup. Basically, any TLog backup taken after the AdHoc backup will now be associated to that backup.  In this case, had the person simply taken the AdHoc backup using the Copy-Only option, there wouldn’t have been any issues with the restore since the chain of backups wouldn’t have been broken.

So how do we take a copy-only backup of a database? It is as simple as just adding a ‘with’  statement to the backup command as seen below.

– Create full backup with Copy Only option
BACKUP DATABASE MyDataBase
TO DISK = ‘D:MyDatabase_CopyOnly.bak’
WITH COPY_ONLY
GO

The copy-only feature has been available since SQL 2005, but had to be written in the T-SQL backup statement. In SQL2008, the Copy-Only feature is available in the GUI for ease of use.

Keep in mind that the copy only feature is not available for Differential backups and the option in the GUI will actually be ‘greyed’ out.  The copy-only feature should always
be considered for any AdHoc backup that is not part of the normal backup schedule in your environment.

I gave 2 sessions, the first one on Networking and Self-promotion in the community. I was excited to have it as one of the first sessions of the day, I tried to focus on networking and meeting people in the SQL community, specifically that event. I had a good amount of people in the session and lots of good questions and discussions. I really tried to encourage
people to go out of their way to meet new people and exchange business cards. The only thing I forgot to mention is to take those business cards and follow up with people through twitter or LinkedIn.

My second session was on Central Management Server and Policy Based Management. It never surprises me that no matter how many times I give this presentation, I always get new questions. I started my session by asking how many people have ever used PBM and to my surprise, only 2 people in the whole room. This might discourage some people, but I see it as a great opportunity to really teach something brand new to people who are interested in the subject. I met some great people in the session and look forward to talking with them again in the future.

By lunch time, all of my sessions were done. I spent the rest of the day hoping from room to room trying to catch some good sessions. Caught one session by Eddie Wuerch (t|b)on Temp DB Tuning and one by Warren Sifre (t|b) on AlwaysOn in SQL 2012. I managed to take away quite a bit from these sessions and look forward to using that info in the future.

The after party was great. It was a very laid back, old school sports bar that had a huge section for all of geeks to sit around and talk about geek stuff, have some beers and continue to network with each other. I am already looking forward to next years event.

Huge thanks to Andrew Karcher (t|b) for the event and all the great info for our upcoming SQL Saturday 144 here in Sacramento, CA!!

If you go to your windows menu, type in PSR and hit enter:

You will see this window pop up.

All you have to do is hit Start Record and it will record a snapshot of every click you make as well as describes everything the user does (the best it can).

Problem Step 1: (3/19/2012 9:58:45 AM) User mouse drag end on “How do I use Problem Steps Recorder? (pane)” in “How do I use Problem Steps Recorder? – Windows Internet Explorer”

A few things to remember with PSR:

* Make sure you minimize the Problem Steps Recorder, otherwise it will be in every snapshot taken.
*By default, the Problem Steps Recorder has a limit to 20 clicks/snapshots. You will have to change the settings for PSR and set it to 100, which is the max.

*Make sure you stop it when you are done, otherwise things will get overwritten. It is a rolling window of snapshots, so at your 101^st click; you will lose your 1^st one.
*Make sure you are running it as an administrator!
*PSR will not record typing, but it does give you the ability to add comments by clicking on the Add Comment.

Hopefully this helps you out and saves some time with documentation and problem solving.

I am coming up on the closure of my active part of the Idera Advisor and Community Educator (ACE) program. Looking back at what I have done and accomplished in the last 9
months has been amazing. I have met and networked with people I never thought I would have, presented to people I never thought I would and I am learning new things that I never thought I would get the opportunity to learn. If you would have asked me a year ago, where I would want to be in 2012, I would have told you out of technology all together. I was getting to the point that I wasn’t enjoying myself and my work anymore. I felt like the life was being sucked out of me, mainly due to where I work. I was turning into exactly what I didn’t want to become; an average everyday DBA with no desire to achieve more. I had two major turning points in my career in the last year, the first being the SQL Cruise I attended with Tim Ford (b|t) and Brent Ozar (b|t) and the second, being selected for the ACE program. Since that time, I have found a new born energy and love for SQL that I never knew I had. In all actuality, I think I have learned more in the last year than I had in the previous five.

Now that my time as an ACE is starting to wind down, I thought it might be a good idea to
tell people who are curious, exactly what I have gotten out of this program thus far. Since its inception, I have had the opportunity to work with 5 other extraordinary people; people I might have felt were untouchable or unreachable in the past. I was not a tweeter, blogger, researcher or expert in anything (at least I didn’t think so). With the help of this program, I have gotten outside my comfort zone and forced myself to meet new people and try new things. I have never been afraid of speaking in front of people or making a fool of myself (as was evident with my SQL Cruise video). My philosophy has always been that you don’t need to be the smartest person in the room, but rather the best at finding the right answers. We wouldn’t be blogging and talking on twitter if we didn’t want to learn and better ourselves. There are only a few people in this community that I think DO know almost everything, but the rest of us are still trying to learn and keep up to date with the constantly changing technologies.

With the ACE program, I have been able to travel to different parts of the country to attend
and present at SQL Saturdays. Not all of us have travel budgets that allow us to get out to other parts of the country like this.  I have made a ton of great connections in many different states now. I have new SQL friends in Colorado, Utah, Washington, Florida and Oregon that if it wasn’t for this program, I would never have met. I have grown my SQL Family into something I am proud of and can depend on. I have a new found love and faith in the SQL community and what it stands for.

If you are on the fence about applying to become and ACE, I would be more than happy to
push you in the right direction. What is the worst that can happen? You don’t get the spot? You name is now in the pot for future ACE spots. The last year has been filled with a ton of new experiences and new beginnings for me. You will never achieve greatness if you don’t at least try!

Get in on the ACE recruitment period, you won’t regret it!