If you've proven yourself on just about any db architecure you should be fine. IMHO, this job is the ability to find answers (on the internet and in books), and be able to apply them. No one that I know can put the whole of the technology into their brain and pull out at will. Always thought closed book tests were dumb when syntax was being tested. Not at all real life. I've never had one situation since school (long time ago) that forced me to memorize syntax...

BTW, 1.5 years ago I was in a similar situation - no SQL2005 (sybase and sql2000) with the prior couple years mostly beuracratic work. Then straight to data architect, one-man show for software development house. I wasn't real confident, but knew I had succeeded in the past and knew how to work hard. Confidence was shaky (also getting older) , but ignored those thoughts and did my best anyway.

I would suggest when you get there to find some "low hanging fruit". Some issues that they want solved, that you can fairly quickly resolve. Don't try to tackle everything at once. Don't automatically tackle the first thing they throw at you - if possible gather multiple issues and then determine which one(s) you can solve quickly. A problematic query or whatever. This will help help you gain some respect early on.

Don't lose hope, look at this as a challenge, work hard, and you might be suprised at what you can accomplish - ONE DAY AT A TIME!

kind of a you-rah note, but a few of my close friends did the same for me when my thinkin got a little stinkin

btw, I really like 2005 - much more than any other sybase or ms versions I've worked on.

jg