First off… just to let everyone know that one can change themes on a Sharepoint that's backended by SQL 2005 as is evidenced by this view: http://www.sbslinks.com/shareview.htm. There was a question in the newsgroup that pointed to a old blog post where someone said you couldn't. As you can see from there.. I can.
But you have to hear the rest of the story of how I spent my Friday night….and here's how NOT to party ..
Okay so first off just a reminder that you need to review the documentation on the web for upgrading SQL 2000 to 2005… http://download.microsoft.com/download/4/0/8/40860507-c351-4308-a876-e1b83ee4e77a/sqlinstallsteps.htm and in particular pay attention to the section that tells you to review this KB article: http://support.microsoft.com/kb/918767/
When you are reading that article…make sure the thoughts that go through your brain are not 'just' that WSUS will stop functioning.. which .. hey it's not a Patching night anyway…who cares… but that when you are running ISA Server 2004 with a msde database that it will stop to function….and not only that …that it will see the failure in logging as not a good thing and go into server lockdown mode.
Uh huh… you can see it coming can't you? The Blonde moment dead ahead.
Oh but wait… you gotta here what else I did…. oh it gets better…
You see.. earlier in the day I had gone into the server room (the one with the lock and the deadbolt you know) and had gotten the cdroms out from the room and taken them back to my office to read the readmes like a good little geek should so Marina would have been proud of me…and I left my office keys in the server room.
So….. 5 p.m comes and the folks at the office pack up …and our dutiful secretary does exactly what she has been told to do religiously every night is to lock the server room door (oh yeah… you see what's coming next… don't you? The truly blonde moment of the evening)
So… I'm in my office about an hour later when I start uninstalling SQL 2000 and I stupidly forgot to flip the ISA to a flat file logging before uninstalling SQL 2000 as the migration instructions don't really wack me upside the face that once I mess up msde for WSUS….. it's also going to mess up ISA. So there I am uninstalling SQL 2000 and I go to confirm that WSUS doesn't work as the instructions say. Which it doesn't as I expected. All of a suddent my IM shuts down (I'm doing this via a TS session at my desktop …not in the server room) and all of a sudden the brain kicks in and I realize that ISA has just gone into lockdown mode… so not only is the Internet dead…but I've just lost TS access to the box. Rats. No problem.. It's just ISA not being able to connect to the database… I'll just go to the server room and log in physically to the server and flip the database to file and I'll be back and running again…as soon as I find my office keys which are…….
…..uh…. they are….. uh…
….. oh yeah….
……locked in the server room…. uh huh…. yeah.
So fortunately I have Outlook in cached mode … oh yeah because the network is like dead… to look up a fellow office mate in Outlook to come back…unlock the server room so I can get my office/car keys.
Okay so one set of office keys later… we are in the server, logged into the physical box which of course is just chugging along happy as a clam and we flip the logging databases of ISA to file and restart the Firewall service which of course stopped.
One delayed migration/upgrade later… we have a Sharepoint who's now backended on SQL 2005 workgroup…
(make sure you read the follow up exact "how to")