It seems like this is the weekend for SQL Server nostalgia. My current project will handle 18 applications based on SQL Server 2005 x86, and I need to dig deep into my memory to find out when I last worked with this version of SQL Server. It must have been in 2006-07.
Lifecycle and server builds
Lifecycle SQL Server 2005 Standard/Enterprise:
- Released: 14-JAN-2006
- Mainstream: 12-APR-2011
- Extended: 12-APR-2016
The latest service packs for SQL Server 2005 is found here.
When I see so many database on old SQL Server version, I become pretty sad and amazed. The database technology has evolved a lot the last few years and with changed licensing and virtualization, customer would most likely save money by upgrading their systems. Paul Randal at sqlskills.com is one of the leading “SQL Master” certified professionals in the SQL Server Community. Earlier this year he had a survey on which server build number people had on their production server. He received information from 3085 servers where people sent the result from the T-SQL command “SELECT @@version” for their production SQL Servers. The result is presented in this post.
RESULT: 51% of all instances in the survey are out of date, by at least not being on the latest SP build, and 53% of all instances in the survey are unsupported.
The installation for SQL Server 2005 is pretty similar as other version, and when I look at it is nice to have all the screenshots in a blog post as I have done for SQL Server 2000 as well.
The first step of the installation is to install pre-requirements for the installation. This includes the native client drivers and setup files. This step has to complte before the installation continues.
The next screen shows a successfull configuration and SQL Server is ready to be installed. There is one warning on the IIS configuration, but this is just a minor warning and this can be configured as a post-installation task.
The next screen shows the feature selection for the components that you like to install for your SQL Server. Select all the components that you need and press “Next”.
The next screen enables you to set up the service accounts for the SQL Server services, such as db engine, agent, analysing services and SQL browser. Normally, you create the service account as a pre-installation task, but for this example, I just use the built-in system account, but this can be configured later asa a post-
The next screen let you decide whether to use windows authentication or mixed mode authentication (windows and sql). This is equal for all version, and if you choose “Mixed mode”, you have to set the SA password.
The next screen let you set the desired collation for the server. The server collation will have effect on the sorting, how strings and numbers are shown in the client and stored in the database.
Nothing real important in the next screen other if you want automatic error reporting to Microsoft, that helps them creating more stable service packs and cummulative updated. In addition, you can report feature usage. This will help Microsoft in their decission process on which features to improve and enhance.
The next screen is just a final step before the installation starts. It is a summary page of what will be installed.
The installation progress will be reported as shown in the screenshot below.
When the installation is completed a screen like the one below. It will show a log file and suggestion on how to continue configuration. In the screenshot below suggestion on analysing services and reporting services.
The Service Pack 4 is the latest one for SQL Server 2005.
Before the upgrade start, the service pack installation wizard will show what components that will be updated.
The installation progress will be show and set a status for each components. The screenshot below shows that the upgrade for “SQL Server Native Client” require a reboot of the server.
The installation will sjow a status when it is completed.