On Thursday Feb 7, 2008 at 8am Pacific (11am Eastern, 4pm GMT) myself and Jason Hall, Systems Consultant at Quest Software will be co-hosting a webcast looking into the challenges in seeing exactly what is happening within SQL Server (including SQL Server 2008) using Spotlight® on SQL Server Enterprise compared to the native tools.
For those who are interested in attending the URL is: http://www.quest.com/events/listdetails.aspx?contentid=6732&technology=&prod=&prodfamily=&loc=4
FIRST TIME USERS: To save time before the meeting, check your system to make sure it is compatible with Microsoft Office Live Meeting: http://go.microsoft.com/fwlink/?linkid=52354
I look forward to seeing you all there.
The SoCal Code Camp was this last weekend. I had a great time attending and speaking at the code camp this time around. I hope that everyone who attended my sessions had as much fun attending the sessions as I did speaking at them. I did my best to make them as much fun and interactive as I could.
As promised here are the slide decks and sample T/SQL code from the four sessions. Everything is within a single ZIP file. I’ve included two copies of each slide deck. One in the Office 2007 format, and one in the Office 97-2003 format. They are identical to each other, but I wanted to include both so that people with the older version of Microsoft Office can see the deck without having to download and install the patch which allows Office 2003 to view Office 2007 files.
The sample scripts which I’ve included are all run against the AdventureWorks database or the AdventureWorksDW database (check the USE commands at the top of the scripts). If they need a different database they will create the new database.
Session 1 – SQL Server Query Tuning (SQL 2000+)
Session 2 – SQL Server 2008 Resource Governor (SQL 2008 CTP5+ only)
Session 3 – SQL Server Service Broker in the Real World (SQL 2005+) (I’ve fixed the problem with the single server script that we were having at the Code Camp. Turns out I had left the route in place which is why the message never showed up. The first script didn’t run correctly because I had run the server to server script on my virtual machine and the route was left by accident.)
Session 4 – SQL Server 2008 What’s on the Horizon (SQL 2008 CTP5+)
If you have any questions about these slide decks or sample code feel free to post a comment here, or drop me an email.
You can install SQL 2000 and SQL 2005 on the same machine. I always recommend that they be installed in this order to try and get everything working as best as possible.
- Install SQL 2000
- Install SQL 2005
- Install SQL 2000 SP4 (Or the latest service pack)
- Install SQL 2005 SP2 (Or the latest service pack)
There are literally thousands of different message boards on the Internet where you can find technical information from fellow IT professionals. When asking questions on these boards there are some basic guidelines which most people like to have followed. They are sometimes informal, but they are fairly common across most of the boards.
- Don’t use topics like “Help!!!” or “It doesn’t work”. Using a descriptive topic will make more people want to read your thread and help you out.
- Be polite when talking to the people who are trying to help you. They aren’t getting paid to do this, so be nice to them. It’s always nice to get a thank you from the poster.
- Check your spelling and grammar. It doesn’t have to be perfect, but many people prefer proper spelling and grammar. (Mine isn’t the best, but I do try.) If English isn’t your first language and people are giving you a hard time about your spelling or grammar some people will be a little more forgiving once they know that you are not a native English speaker.
- If the message board is in English and you are posting an error message which is in another language, please translate it to English. More people will be able to read it that way. You may not get the translation perfect, but it’s usually close enough to get the point across.
- Don’t post just the error number. There are thousands of error messages and we need the entire error message.
- Don’t just say that it’s broken. Be specific about what isn’t working.
- Let the readers know what you have done to try to fix the problem already. That will save you time as the people trying to help won’t have to have you try stuff twice.
- If you find the solution your self post it to the thread. This will help the next person who has the same problem. These forums are all about helping others and this is a great way to give back to the community.
- Please remember that the people responding aren’t computers. It may take time for someone to read your thread who knows the answer.