I'm installing SQL2005 Enterprise right out of the box on a fresh install of Windows Server 2003 R2. Installing Prerequisites is the first dialog. This includes the .NET Framework 2.0, SQL Native Client, and "Support Files". The Frameworks is a no brainer: we'll need that for the CLR integration. SQL Native Client is a new direct data access client. Funny that after so many years of generifying things with ODBC and ADO that we are again going with proprietary clients. I like it actually and it's not that new, "Classic" ADO.Net also had a specific SQL Client. The "Support Files" is a little ambiguous though. I wonder what's really in there. There has been some disscussion around the office lately about where exactly SQLCMD.EXE comes from and if it's redistributeable. I have yet to find any good answers for that, but perhaps "Support Files" is where this useful command line utility resides. I wonder if you need a license to install the prerequisites? Hummm. More on this later when we start talking about deploying database objects.
I'm running into an odd thing. The MSDN DVD that I have from MS that says it has ISOs of all the various SQL 2005 installations does not have an ISO for the enterprise edition. It has a set of folders directly on the DVD. That's extremely inconvenient because I'm installing to a Virtual Machine. So I have to copy down a huge folder of installation packages to my VM to run the install and later delete. Thanks guys. And don't even think about exposing your DVD drive via Remote Desktop – you can't do installs that way (a good thing). ISOs are indicated here, file folders are "so last week".
Well, to answer the question about SQLCMD.EXE, it is definitely not installed with the "Support Files". I searched my HD after installing the prerequisites and it's not there. Bummer.
The System Configuration Check is the next setup dialog and it gave me two warnings:
- Minimum Hardware Requirement (Warning)
Messages
- Minimum Hardware Requirement
The current system does not meet the minimum hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.
- IIS Feature Requirement (Warning)
Messages
- IIS Feature Requirement
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
The first is prolly talking about my memory footprint. I only gave this VM 512MB RAM, so I'll restart it with 1 full 1GB and see if that helps. The second is telling me I should add the IIS application role to this machine if I would like to add all the Web Service hooks. I do, but it's nice to see that it's not a requirement. Sometimes a database should just be a database.
Installing IIS is as easy as adding an Application Server Role to the server using the Management Interface. It will squawk for the "Service Pack 1" CD, but it's really talking about the Windows Server 2003 R2 Disk 1, so I load that ISO into the CD of the Virtual Machine. Lucky for me, I have it lying around in my c:\vmroot folder on the Virtual Server, so no file moving is required. I checked the boxes for Front Page Extensions and Install ASP.Net because I don't know any better. I'm hoping that Front Page Extensions are not used, but you never know. In a production environment, I'd avoid FPE.
Unfortunately I have to shut down the VM to change the RAM size. The next version of Virtual Server should let you change this on the fly.
With IIS added to this VM, and double the RAM, I'm ready to try again. I notice that I completely read the whole "Support Files" thing wrong. Those are "Setup Support Files" so just ignore me on that tangent. The System Configuration Check is all green lights and I'm on to installing components. I select everything: Database Services, Analysis Services, Reporting Services, Notification Services, Integration Services and workstation components. I actually plan to run the workstation components from a client machine, but I'll put them here anyway. I'm selecting the built-in service account of "Local System" to run my Default Instance rather than a Domain Account just to keep things simple. I'm selecting Windows Authentication only mode for my server. SQL Logins give me the heebee-jeebees. Everything else is pretty standard. This install is a long one so this post will be in two parts…
0 comments:
Post a Comment