Author: way0utwest

This is one of the reasons that I don’t like to put CTP software (or Beta software) onto machines that I can’t take the time to wipe and rebuild. Buck Woody wrote a note about upgrading your CTP, and the short answer in his blog is:

NO

You can’t upgrade a CTP and it’s not supported. Well, maybe you can upgrade a CTP, but it’s a bad idea. There could be settings, registry entries, etc. that get stuck from the CTP into the RTM, and it might bite you later.

I don’t think it’s worth the risk. Honestly SQL Server is easy to detach dbs, script logins, uninstall, reinstall, fix it up. It’s a simple process, even if you have jobs, so I wouldn’t complain about it, wouldn’t chance it, and just rebuild the SQL instance.

Here’s what I’d do if you don’t want to rebuild Windows

1. Perform a physical to virtual migration using Hyper-V. This will give you a backup.
2. Script out logins, jobs, save packages on the file system. If you have linked servers, do those as well. I might do a complete script of the server if you can.
3. Detach the user databases.
4. Uninstall SQL Server 2008 R2 CTP (or whatever version). Make sure you get all Control Panel SQL Server entries.
5. Delete the registry keys that might exist.
6. If the user databases are in default locations, move them. Delete the folders from the file system.
7. Reboot
8. Reinstall SQL Server
9. Attach databases.
10. Run scripts to add logins, jobs, etc. Fix orphaned users.
11. Test, test, test,

Easy-peasy

I installed a new VM with SQL Server in it, along with Win 7 and Reporting Services. The plan was to mess with this as a detailed journey through to learning more about SSRS this year.

I was excited to get going on this new install since I hadn’t messed with SSRS much since 2005, and then on one of our test servers for SQLServerCentral. So I fired it up, having run through the installation defaults and browsed to the Report Manager to get:

Seriously? No IIS on a default install, and SS2K8 SSRS shouldn’t require it. I’m an admin on my own box, so what’s the deal. Actually this is a Firefox issue that requires that I clean up a few things and store off the name password.

However, once that was done, I connected and found a blank report manager screen. That was very, very annoying.

At first I was fairly torque’d. After all, this is a dev setup that’s common, and having stuff not work like this really doesn’t do the SSRS brand much good in the eyes of developers.

Now I’m not on a domain, I’m standalone, which is likely not common. It’s also probably that the DBA sets up SSRS on the server and developers connect, but I think lots of them have local instances to test reports against.

So what do I do? I dug around the Internet and found a lot of fragmented advice. The big one was that I needed to setup roles for SSRS, but I had to use Report Manager to do that. And as you can see above, there’s no “Properties” tab above. The final advice that seemed to work for me was a need to log in as administrator. Not an administrator, but as administrator itself.

How do you do that in Vista or Win 7? Administrator is buried on those OSes, and for good reason. Otherwise people would likely use it all the time. I tried running IE as Administrator, but that didn’t work. That was one of the first suggestions I’d see, so I had to log into the machine itself. To do that, first you need an administrative command prompt.

Then you run this: “net use administrator /active:yes”

When you then do a “switch user” and get the login screen, the administrative account is visible. I logged into that, connected to Report Manager, and added my account as a content owner and publisher.

Back to my account and I’m golden. I can now see my main screen.

I’m not sure why the IE-as-administrator did not work, but if it fails for you, this should help.

I have been a fan of 37 Signals for some time, and I read their blog regularly. I think they go a great job of writing about how to run a business and not build an investment.
Rework is a summary of quite a bit of advice from their blog that has been rewritten and compiled. It’s a business book that give you advice on how to start your own business, how to hire people, how to get motivated in a real way.
This isn’t the book for someone that wants to start a company and sell it for a million dollars. It’s not a book that helps you get rich quick. It’s a book that tries to get you to think about how business actually works, build something that you are proud of, and something that succeeds.
The book is a series of chapters, each broken into short 1-2 pages snippets of information on a particular topic. Each section has an illustration from the 37 Signals artist, all of them quick sketches, and many of them humorous looks at the topic.
You could get all of this information from their blog, but it’s nicely summarized and edited in this book. It’s not a reprint of the blog, it’s a rewrite of the same information, but cleaned up. They talk about how their initial draft was twice as long, but then cut down the verbosity to get to the meat of the topics. That’s advice they give you for business as well. Don’t use more words than you need.
Something I need to learn.
This is a great business, book, in my opinion. One that’s worth reading if you are even thinking of starting your own business.

I saw this article on the improvements from E-ink that are coming. There are two videos, one of a better screen that can handle simple animations, likely getting into actual products you can by in about a year (early 2011).

The other was low power, but more durable. The guy in the second video smashes a fist into the screen.

Impressive.

I like the idea of e-ink, but after having a Kindle, and and  iPhone, the iPhone just works better.