So at the point in this pic, it's already gone through all of the features and listed them as 'In Progress'. Then it listed them as 'Pending'. So looking at the underlined section there, it looks like nothing is going to be marked as complete until the entire install is done. It's a little annoying cause it would be nice to see the actual progress.
OK, the install is finished now. And it requires ANOTHER reboot. The SQL program menu didn't show up on mine until I rebooted.
So the bottom line is this... the install isn't bad, but it's not exactly what I'd call smooth. All the reboots are ridiculous, and it takes quite a while to install.
Frankly, Oracle 11g is still beating the pants off of MS in terms of an easy install. We should be able to point to a default install with very little intervention. I didn't see a place to record an unattended install so I'll be looking at install in detail on my actual servers over the next few days. So while the install isn't bad, SQL2K was actually easier to install.
One thing I wanted to make sure I tied into install was the user account list. Remember in that pic above where I was able to assign a windows user account to SQL? I was hoping that meant that the builtin\admins group was gone by default inside SQL, but it's not. It would've been very nice for the install to add my service accts as logins, and whatever user accts I added manually on that screen, and left builtin\admins out. That would have made for a nice, secure default install. Oh well... maybe next time.
Ok, I'm going to go play with install some more and let you guys know what I come up with.
Watch my free SQL Server Tutorials at:
Read my book reviews at:
Blog Author of:
DBA Rant – http://dbarant.blogspot.com