Sql 2005 Installation (part 2)

OK, a few days later and I'm not really sure where I stopped. I'll fire up the VM and see where we are at…

Looks like SQL completed installing on the server, and I'll test that by remoting in and launching the SQL Server Management Studio, connecting to localhost and there I see databases. All is good. Now I'm not really hip to running all the client tools on the server, so I'm going to install just the client tools on my client workstation, laptop, whatever. In my case it's a AMD Shuttle running the Vista CTP, so I'm taking some chances using beta software. I'd suggest using an XP box or another Windows 20003 Server instance. Either way, it a good idea to get the client tools on a client and the SQL Server on a server.

The client tools setup screen default to installing nothing. So I'm going to select Management Tools, Business Intelligence Development, the SDK, and SQLXML from the Client Components group as well as Books Online from the documentation. If I need the sample databases later, I'll get them when I need them. I prefer to build up my databases from scratch so I can really feel the pain.

Something I'm completely ignoring here is security. In my lab environment I'm a domain admin. It's typically a bad idea to run with such privileges, but I'm more concerned with feature additions to SQL Server 2005 and I will be creating a variety of lowered privileged user accounts as we go.

Client Setup is complete and I'll verify my connectivity the same way I did on the server, by running the Management Studio and connecting to my instance using the server name of NOSQL2005. You should use whatever machine name you installed you instance on.

The Management Studio in the replacement for Enterprise Manager and Query Analyzer from SQL 2000. The Business Intelligence Studio is an IDE for creating SSIS Packages that replaced MTS Packages. There are some pretty fundamental shifts in this version. As I understand things, MTS and SSIS are so different, that there is no upgrade path. You basically need to rethink and rebuild. This should be a major bummer for organization that reply heavily on MTS packages and SQL jobs. There may be quite the market for good SSIS developers over the next few years.

That's it for getting set up. We now have a client machine, a server set up on a virtual machine and all the software loaded. We will be taking "A Developer's Guild to SQL Server 2005" one chapter at a time recreating each example. This could take months J