System Requirements
* O/S : Windows2003 with sp2/ 2008 Server
* Memory : 1GB
* CPU : >1GHz
* HDD : 2684MB
: 611MB for database server
* SQL Native Client
* .Net Framework 3.5 with sp1
* Windows Services
:WMI (Windows Management Instrumentation)
:RPC (Remote Procedural Call)
:DTC (Distributed Transaction Coordinator)
Installing SQL Server
* SQL Server supports 2 types of installations
1. Stand Alone Environment
2. Cluster based ,,
1. Stand Alone installation
Steps
* Creating service account
* R.C on My Computer --> Manage
* Local users and groups
* R.C on Users
* New User
Name: SQLDBEngine_user
pwd hyd@123
Confirm p hyd@123
Uncheck "User must change...."
Click on Create button
* Go to SQL Server dump or use DVD
* Double click on Setup
* Click on "Installation"
* Click on "New Stand Alone ........"
* OK
* Under Setup Support Files --> Click Install
FAQ: - I am installing SQL Server in d: drive where 20GB free space is available. But in system drive (c:)
there is 100MB free space. Setup continue or fail?
Ans:
* Setup support files are installed in system drive where 118MB free space is required.
Setup fails.
* Next
* Under Installation Type select
Perform a new ............. option
Next
* Next
* Select "I Accept........"
* Next
* Under Feature Selection
select
Database Engine Services
SQL Server Replication
Full Text Search....
* Next
Note:
1. First time, select shared features also
2. Install SQL Server always in NTFS not in FAT32. NTFS provides high security and high
performance.
* Select "Named Instance and enter: TEST
Instance Root Directory: d:\SQLSERVER
Next
* Next
* Under "Server Configuration" Click on button
Use Same account..........
Enter
Account Name: SQLDBEngine_user
password hyd@123
OK
* Next
FAQ:- Once I install SQL Server what are the logins created automatically?
Ans:
SS 2005
* sa
* BUILTIN\Administrators
SS 2008
* sa
* Login for service account
* Logins for added users in wizard
* Under Database Engine Configuration
* Click on "Add Current User"
* Next
* Next
* Next
* Install
FAQ: - What are the differences in the installation of SS 2005 and SS 2008?
Ans
* In SQL Server 2005 there is no
* Installation Center
* Upgrading, edition change, rebuilding system databases etc we have to perform
by running setup from command prompt.
* There is no "ConfigurationFile.ini"
* Next
* Close
Post Installation Steps
1. Verifying installation
* We can verify installation process using Summary.txt file, present in
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log
 |
2. Verifying instance folders
* For every instance the following folders are created in installation directory.
MSSQL10.<instanceName>
MSSQL
* BACKUP
* Binn - Consists of .exe and .dlls
* DATA - data and T.log files
* FTData
* Install - consists of .sql files
* Jobs - jobs and maintenance plans
* Log - Error logs
* repldata- Replication snapshot folder
* Upgrade (2008)
3. Configuring Error logs
* Error logs maintains events raised by SQL Server.
* Consists of both errors and information.
* Error logs are present in LOG folder of respective instance.
* SS supports
1 Current Log
6 Archieve logs by default.
* Current Log has all the events from server restart.
* Once the server is restarted all the events are flushed from current log into Archieve1 and from
Archieve1 to Archieve2 etc. This process is called recycling error logs.
* We can recycle error logs explicitly without server restart using
sp_cycle_errorlog
* We can read error logs using sp_readerrorlog
* SS supports min 6 and max 99 error logs
* How to configure?
* Go to SSMS --> Object Explorer --> Management
* R.C on SQL Server Logs --> Configure
select checkbox "Limit no of ............"
Maximum logs..........: 20
* OK
FAQ: - When I am starting SQL Server it was not started successfully. What are the possible
scenarios? and how to troubleshoot it?
Possible Scenarios
1. Logon Failure
* Problem with service account.
2. 17113
* Master files are moved or corrupted
3. 3417
* After moving master files we have not granted read/write permissions on new folder
* Or any one startup parameter is missing.
How to troubleshoot?
* Check windows event log
* start --> run --> eventvwr
* System
* In the right pane double click on Error
* Using SQL Server error log
* Go to LOG folder of respective instance
* Open ERRORLOG in notepad and check for errors
No comments:
Post a Comment