Skip to main content

Pragmatic TSQL Programmer

Go Search
Home
  

Greg Wilson's thoughts from the trenches of TSQL and C# development
"The SQL Server 2005 Express Tools are installed. To continue, remove the SQL Server 2005 Express Tools."

I'm copying this from something I found on Chris Crowe's Blog. I'm copying it because I can no longer access his blog and am having to rely on Google's cache of the page to get the info:

 

You may find that when installing SQL Server 2008 you receive the follow error during installation.

"The SQL Server 2005 Express Tools are installed. To continue, remove the SQL Server 2005 Express Tools."

A couple of things to do:

  1. Remove SQL Server 2005 Express Tools
  2. Remove Red-Gate SQL Prompt if installed.

   

UPDATE:

SQL Prompt v3.9 (available for download from www.red-gate.com) addresses this problem and no longer blocks the installation of SQL Server 2008. Also, SQL Prompt v3.9 supports SQL Server 2008.

Tanya Joseph
Red Gate Software Ltd

It's official
Not only is SQL 2008 RTM, but I'm a genious!
 
 
I am 12% Idiot.
Friggin Genius
I am not annoying at all. In fact most people come to me for advice. Of course they annoy the hell out of me. But what can I do? I am smarter than most people.
“Becoming the SQL Guy” – Demos and Slides

Here are the downloadable demos and slides from the "Becoming the SQL Guy" presentation that I did at the Iowa Code Camp. It was a great session, and I had a great audience. I will be doing a lot of updating to this blog in the next few days, so stay tuned!

Downloadable .Zip File

It’s going to be a busy a busy year for speaking

Looks like my spring will be fairly busy speaking at various events. In just a few weeks (February 6th), I am heading to Omaha to speak to the Omaha SQL Users' Group. In March, I'm going to be doing (and recording) an on-line presentation for the programmer community at Arstechnica.com. Then, April 5th I will be in speaking at the Twin Cities Code Camp. Then, of course, I'll be speaking at the Iowa Code Camp on May 3rd. It will be a busy spring.

My plan for the spring is to develop the presentation that I've always wanted to give: "How to become 'The SQL Guy' in your organization." It is a definite departure from the typical "look at me and how much advanced stuff I know" type presentation that I tend to see at conferences. I've heard lots of feedback from attendees, especially on SQL topics that they see too much fancy stuff that they won't get to use in their daily jobs, and not enough of what they need every day. My goal is to create the presentation for the average developer who learned a little bit about SQL in college or while learning .NET, but never really advanced beyond the basics. I'm going to try to make it a very example/problem based presentation, where (when possible) I'll take something you might expect to see a novice developer create and then "fix" the code with better TSQL and a better data access layer. I think it should be a lot of fun, and I'm hoping it is something that developers can use right away when they get back to their offices on Monday.

I'm crossing my fingers that I will be able to re-use big chunks from presentation to presentation, and avoid my personal propensity to keep rewriting my presentations and adding new content.

Speakers for the Iowa Code Camp

After scratching around the idea of an Iowa Code camp since last October, we finally are moving forward with a plan. We (the DSM .NET community) and the Cedar Rapids community are going to team up to do some code camps. We are planning the first one on May 3rd at the University of Iowa's new conference center. We are looking at 4 tracks of 5 sessions each. Chris Sutton is handling the facilities and logistic, Javier Lazano is handling sponsorship and acquiring free lunch for the attendees, and I will be in charge of speakers. If you are interested in speaking please let me know ASAP. (Note: In the first 72 hours of planning this, we already have about 50% of the needed speakers.)

I will be keeping this post updated with the most recent information on the event.

Back 2 Blogging

I realized it has been a while since my last post, but I figured it would be a great time to get back to adding some new content. Last week I wrapped up an 18+ month contract with Wells Fargo and on Monday I am starting a new full time position with Ontuet doing some pretty interesting work with the supply chain of the hardware industry. The workplace looks pretty interesting and I'm looking forward to working with them on their upcoming projects. They are small Microsoft shop with a pretty tight-knit group of employees and a casual environment. I've got several other posts that I will probably get up in the next few days. I've got some cool info on some local code camps and other stuff that I've been working on.

HDC07 Slides and Demos Posted
Thanks to all the 200+ people who attended my breakout session at the HDC.  This has been a really great conference, and hope everybody enjoyed it.  All the code and the slides can be downloaded here.  (Topic:  Expanding your development environment with SQL 2005)
 
I'll post more later, but I''m watching a great talk by Scott Guthrie about ASP.NET 2008, and I'm going to get back to listening to him.
Service Broker Error 15404

Just a quick post while I'm hammering out the last details to my HDC presentation: I learned something new about service broker that I thought should get posted. Admittedly, it probably will not ever be useful in a production environment, but it may certainly help out some presenter somewhere. If you use service broker on a SQL server that uses Windows authentication, and you are on a domain machine that is NOT currently connected to the network, service broker will send all messages to the Transmission queue (the undeliverable queue) until you reconnect to the network. Quite obviously, production machines are not likely to need to disconnect from the network and be unable to communicate with the domain controller. But, laptops that you plan on using for demos at conferences do. And that has led me to panic for the last couple hours to determine why my demo that worked so pristinely for so many test runs suddenly hurls when I took my laptop off-network to practice my demo.

So, for the record, SQL service broker cannot deliver messages if it is using Windows authentication and cannot connect to the domain controller.

Once HDC is over, I'll get back to writing Part 2 of CTEs and performance, but I thought it would be useful post this for any other poor presenters who might be struggling with the same issue.

Common Table Expressions and Performance, Part 1

When I first read about Common Table Expressions in SQL 2005, I saw mentioned that they could increase performance, because the query optimizer could take advantage of existing indexes while a SQL 2000 style temp table could not. For the first several months I used CTEs, I never really investigated this idea. I just assumed that since CTEs were new, they would be faster. (Pretty bad assumption on my part.) After spending all the time that I have on optimizing my production database, I've found that CTEs generally change performance anywhere from a 90+% increase in speed to a order of magnitude decrease in speed.

First off, I did find some situations you could just about guarantee a healthy speed increase: recursive queries. The application I have been optimizing has a lot of tree structured data. I had several heavily called user defined functions and stored procedures that were originally written in SQL 2000 with while loops and temp tables. Moving them over to recursive queries showed consistent performance increases, from 60-90% increase in speed.

Beyond that, CTEs were hit and miss as far as performance goes. More on that in Part 2

Iowa State Cyclones Beat Iowa Hawkeyes

Just thought I'd make sure to publicize the fact that, once again, the Iowa State Cyclones (who came in as 17.5 point underdogs) defeated an over-confident squad of Iowa Haweyes 15-13. Watching the game, the game was not nearly as close as the score indicated. The Cyclones dominated most every statistic, and the Hawkeye linemen were getting pushed all over the field at the whim of the Cyclones. More details here.

A Hawkeye friend of mine said, "But next year we'll beat you for sure!" To which I replied, "If you do, and you beat us again the next year, and the next year, and the next year after that, the Hawkeyes could get back to 500 since '97!" 'Nuff said.

Not SQL related, but I couldn't help it.

1 - 10 Next

 ‭(Hidden)‬ Admin Links