Bru Medishetty's SeekWell Blogs
Posts tagged Installation
What components do I need in SQL Server ?
Feb 4th
I was asked the following questions by many people personally and see this appear over forums repeatedly.
When I install an additional instance of SQL Server on the same machine, what options do I need to select ? What components need to be installed to use basic SQL Server while learning (well sometimes at the job also).
Well it always depends on what one needs on his/her system that decides what needs to be installed. I would make a general assumptions and give the suggestions.
A user can choose to install multiple instances of SQL Server on a single machine, but every instance need not have all the components installed. For example when the first instance was installed only database Engine was chosen since there was no necessity for the Analysis and Reporting Servers at that point. When the need for either of these arises, an additional instance can be installed and only that component can be selected to install, choosing Database Engine is not mandatory here.
Similarly when installing Database engine, Replication and Full Text Indexing are not mandatory, you need to choose them only if you need.
And then finally there are somethings that are Instance aware and Instance unaware. Let me explain that..
Instance aware components are those that can be installed with each instance on the machine and are independent from the other instance, such as Database Engine, Reporting Server and Analysis Server. An instance of a database engine can run while another instance is stopped, in that way they are independent.
Instance unaware are those which can be installed only once per a machine and cannot be installed additionally along with a new instance, such as Integration Services, SQL Server Browser, Books Online, Management Studio, BIDS and client components etc. When these options are chosen to be installed with a newer instance, you are give with a message that they will not be installed and the Installation process moves forward..
One additional point, it is possible to have multiple versions of SQL Servers running concurrently on the same machine.
– Bru Medishetty
Certification Exam – Second Shot Free offer is back !
Jan 28th
One of the popular offers I always liked while pursuing a Microsoft Certification is once again back. The second shot offer gives the candidate an opportunity to have a second shot of the same exam at no additional cost (if the candidate could not successfully pass in the first attempt).
I am planning to take the MCITP : Database Developer 2008 exam and hope to use this offer as it gives me a cushion (If I cannot successfully pass at the first instance).. So I am rushing for a coupon…, remember the coupons are available for a limited time only. The offer is valid up to June 30, 2010. for more information visit promteric web site Here or Microsoft website Here
– Bru Medishetty
Side by Side Installation of SQL Server
Dec 18th
Many SQL Server users (starters and intermediate level users) have a common doubt about the possibilities of installing multiple SQL Server instances on a same physical server. The answer is a cautious yes; the reason for being cautious is, not being sure about the behavior of the application(s) using the previous version of SQL Server. Such a setup is called Side-by-Side installation. It is possible to have multiple Versions of SQL Server Instances on the same machine and also multiple editions of same version of SQL Server.
In the picture below you see that on the same machine, 4 SQL Server instances have been installed and 3 of them are SQL Server 2005 and the other being SQL Server 2008. Each one of the Instances is different from the other.
I used multi-server querying capabilities in SQL Server 2008 to find the information of all the servers in a single query. Coming to Side by Side Installations, it must be noted that this might be required when performing an upgrade on the same machine as the current one. This requires no additional hardware for setting up another system, but on the other hand, there is a risk factor in this, if the installation of the newer instances is unsuccessful and the system becomes unstable or the newer version of executables have known / unknown issues with respect to the working applications.
The decision to go for a Side by Side Installation or a new installation on a seperate system, varies. If it is being performed on a test server for some testing additional functionalities or features it would be a worth a try. Whereas performing this on a system which cannot have downtime, it is not worth a risk to take.
–Bru Medishetty
Installing SQL Server 2005 Service Pack 3
Sep 9th
In this Blog we shall take a look at the steps to be carried out for Installing Service Pack 3 for SQL Server 2005.
Before Installing SP3
Keep in mind to read the Microsoft Technet Articles related to Installing Service Pack 3 for SQL Server 2005. Once installed, the SP3 cannot be uninstalled, you need to completely install SQL Server 2005 Instance from the ground up. Keeping this in mind, always take a Backup of all the System and User Databases on that instance for rollback purpose.
A copy of the Service Pack 3 can be downloaded from the link. SQL SERVER 2003 SP3
Look at the list of bugs that are fixed in SQL Server 2005 SP3 Here
After downloading the executable, go to the directory where it has been downloaded / copied. Double click the executable or right click the Exe File and choose Open in the menu as shown below.
The program finds the Instances installed on the Server.
After the step, the following Dialog box is displayed which is a welcome screen. Click Next to continue…
The Next screen is the License terms for SQL Server 2005 SP3. Choose the option I accept the agreement upon which, the Next Button will be active. (The image below was a screen shot of the default screen of the dialog box)
The next dialog (which is displayed above) provides a list of the Installed components which are available on the current Server. You can make a selection of only those required components to which you need to install the Service Pack. Here, I selected INSTANCE1 which is the Database Engine and other individual components such as Integration Services, Client Utilities etc.
This is one of the advantages in installing a Service Pack in SQL Server. It enables to you apply the Service Pack on a test Instance and test it thoroughly without affecting the other Instance on the same Physical machine.
After making selection of the components to be applied, click Next.
Choose the Authentication Mode to apply the Service Pack, you can choose either Windows Authentication or Mixed Mode, either way the Login needs to have administrative rights on the Server. Click Next
The Error and Usage Reporting Settings are the similar settings you find when Installing a initial Installation of SQL Instance.. Choose what ever applies.
The above dialog displays all the Services that related to SQL Server and running currently, It is suggested that the services are stopped in order not to have a reboot of the SQL Server. I remember, I choose not to stop the Services, and resulted in a reboot., so keep in mind the selection of the choice..
The above dialog box is a summary information box indicating it is ready to start the installation of the service pack. By clicking on the Install Button, you are going to start the Installation, it would not be possible to stop the installation after you click on the Install Button.
The Installation would continue to update the Service Pack for the Individual components as shown in the pictures, above and below.
That concludes the Installation process of Service Pack 3 for SQL Server 2005. Restart the Server to complete the SP3 installation to take effect.
Note: The steps described in this blog are generic, it may be different depending on your environment.
Word of caution: Always perform the installation in test environment and check the SQL Server functionalities and applications that are depending on the SQL Server.
Bru Medishetty
Installing Sample Databases in SQL Server 2005
Aug 10th
You can install sample Databases when Installing SQL Server Instance, if that was not done, you need to install Sample Databases separately.
In this blog, we will look at the steps in doing that.
As the first step, download the Sample Database that would like to install, I chose AdventureWorks for SQL 2005 in this example.
You can follow this link to download the Sample Databases
Remember the path you downloaded the file to.
Browse the directory where you have downloaded the file, select the .msi file , right click and choose Install. (Picture Below)
The Installation process starts and we will look at each of those steps.
If the Security warning Dialog Box appears, choose Run. (Picture Below)
The welcome screen for the Installation Wizard is displayed, click Next. (Picture Below)
In the License Agreement Dialog, Choose I accept the terms to continue.
The Next Screen displays, the Destination Directory where the Sample Database would be installed to.
By default it will be Data Directory of SQL Server. Click Next to continue and Install in the default Directory.
Click Install to begin the Installation.
When the Installation is completed, the below shown dialog Box is displayed and click Finish to complete the Installation.
Once you finish this step, you can check whether the Sample Database is installed by going to the Data Directory of your SQL Instance.
Both the Data and Log files are placed in the Data Directory of the SQL Server Instance by the installation that we performed.
Once this part is done, the next thing we have to do is open SQL Server Management Studio (SSMS). In the Object Explorer, Right click on the Databases Node and select Attach.
The attach databases dialog box appears and click Add Button.
When you click the Add button, there will be a window that requires us to locate the .MDF File. By default, it opens the Data Directory of the SQL Instance, so if the AdventureWorks Database Data File (.MDF) is available, select that .MDF File.
After the MDF file is chosen click OK, it will show the Attach Databases dialog box with the details of the MDF file and also the details of all the Database files (Both Data and Log)
Click OK to complete the attaching the Database.
Now you should be able to see the Database in the Databases Node in Object Explorer.
– Bru Medishetty
http://learnsqlwithbru.com/images/Adventure10.jpg
Recent Comments