270 likes | 518 Views
Installing, Upgrading and Configuring SQL Server 2000. Palak Patel. Pre-installation Considerations. Hardware Requirements Software Requirements License Mode Collation Sort order Unicode support Network libraries User accounts Default and Named Instances Installation Path
E N D
Installing, Upgrading and Configuring SQL Server 2000 Palak Patel
Pre-installation Considerations • Hardware Requirements • Software Requirements • License Mode • Collation • Sort order • Unicode support • Network libraries • User accounts • Default and Named Instances • Installation Path • Upgrade Vs. Side-by-Side Installation • Components
Hardware Requirements • Different Edition Runs on Different Operating Systems • Hard Disk Space: 270MB + space for databases • Memory: 64MB
Software Requirements • SQL Server CE • Runs on Windows CE • Personal • Runs on Windows 9x/ME/2000 Pro • Developer • Runs on Windows NT/2000 • Standard • Runs on Windows NT/2000 Server • Enterprise: • Runs on Windows NT/2000 Server • Clustering will be possible only on Windows 2000 Advanced Server
Licensing Mode • Per-Processor – License required per processor on server computer, unlimited clients can connect • Per-Seat – License required per user
Collation • Collation is a set of rules that Windows users to support characters and locations • SQL_Latin1_General_CP1_CI_AS matches best with SQL Server 7 • Collation of a server can not be changed once installed, however you can create a new database with a required collation • SQL Server 2000 supports Unicode characters
Sort Order • The sort order determines how the data is stores, compared and retrieved during queries • Dictionary order, case insensitive • Dictionary order, case sensitive • Binary order • Note: If you choose case insensitive, all the password for SQL Server are case insensitive and if you choose case sensitive, all the passwords are case sensitive
Unicode Support • SQL Server 2000 supports Unicode • The default unicode support is case-insensitive, width-insensitive and Kana (Japanese) insensitive • Use default unless you really require it • If you need to support multiple languages but need to use 850 & 437 character sets, you can choose unicode as a data type when you create columns in your database
Network Libraries • TCP/IP (Default) (Standard Port: 1433) • IPX/SPX • Named Pipes (Default) • Multiprotocol • AppleTalk • DecNet
User Accounts Accounts for • SQL Server Service • SQL Server Agent Service Typical Options • The advanced logon as a service right • Password never expires checked • User must change password at next logon cleared Create User Accounts prior to running installation using AD Users and Computers if using Win2K, User manager for Domain if using WinNT and so on…
Default & Named Instances • Instance is a single installation of SQL Server. Two Types (1) Default (2) Named • Default Instance • name of SQL Server is the name of the computer • SQL Server 6.5 and 7.0 can be installed only as Default instance • If you computer name is SER200, the default instance will be accessed as SER200 • Named Instance • Multiple copies of SQL Server will be running simultaneously on a single computer • You can name the instance e.g. Dev on SER200 will be accesses as SER200\Dev • Up to 16 instances supported
Upgrading Vs Side-by-Side Installation • If SQL Serve 6.5 is already installed, the SQL Server 2000 Setup program will attempt to upgrade the installation by default. SQL Server 6.5 requires SP5 to be upgraded. You can also install SQL Server 2000 in another directory and run both of them at a time. Use Upgrade Wizard to move databases later. • If SQL Server 7 is installed, you can upgrade or install SQL Server 2000 in another directory
Selecting Components • Choose what you require to install during custom setup
Installing SQL Server • LAB: Installing the Default Instance • LAB: Installing the Named Instance
Unattended Installation Files on SQL Server 2000 CD-ROM: Modify Setup.iss as reqd
Testing SQL Server Installation • Inspect Program Group • Check Enterprise Manager • Check Service Manager, inspect the services • Run a Test Query in SQL Query Analyzer
SQL Server Services • SQL Server (MSSQLSERVER) • SQL Server Agent (SQLSERVERAGENT) • Distributed Transaction Coordinator (MS-DTC) • Microsoft Search
Installation Path Default Folder for Backup Files Program Files Data Files Installation Scripts Used by SQL Server Jobs SQL Server Log Used by Replication Used by Upgrade scripts and output
Upgrading SQL Server 6.5 & 7 to SQL Server 2000 • 6.5 and 7.0 can be upgraded Directly • Earlier versions like 6.0 and 4.21 needs to be upgrade to either of the above before it can be upgraded to Version 2000
One-Computer Vs Two-Computer • Install SQL Server 2000 on the second computer and migrate data from version 6.5/7.0 to 2000 • Leaves the mail server untouched • Requires additional server
Upgrading Vs. Side-by-Side Installation • Side-by-Side Installation allows to run 6.5 or 7.0 simultaneously with Server 2000 • Migrate databases and option leave the databases on 6.5 and 7.0 during conversion • Requires hard drive space, memory and processing resources to run both (6.5 or 7 and 2000 simultaneously)
Switching between 6.5, 7.0 and 2000 • 6.5 and 7 allows to run only Default instance at a time • 2000 allows to run multiple instances • Can run 6.5 or 7.0 default and 2000 named instance simultaneously • Can not run 6.5 and 7.0 simultaneously • Comes with a Switch Version program
Upgrade Pre-requisites From Older Versions to 2000 • Service Pack 4 for Windows NT or Windows 2000 • Service Pack 5 for SQL Server 6.5 • Internet Explorer 4.01 or later • 256MB of RAM • 180MB on Hard disk for Program Files plus 1.5 times the size of the databases being upgraded • If upgrading earlier versions than 6.5, first upgrade to Version 7.0
Upgrade Issues Objects are not created in the new databases due to • The object has been rename using sp_rename • The accompanying text in syscomments is missing • Stored Procedures has been created with in other stored procedures • The owner of an object’s login ID is not created at the new server • Older server has Integrated Security and you have not created necessary groups on new server Some other issues • The upgrade process with fail, if @@SERVERNAME returns null • Stored procedures that reference or modify system tables will not be converted • Servers involved in replication must be upgraded in proper order
Configuring SQL Server • SQL Server Settings • General, Memory, Processor, Security, Connections, Server Settings, Database Settings, Replication and Active Directory Tabs • Configuring SQL Network Protocol Settings • Configuring ANSI Settings (Server level and database level) • Installing SQL Server Clients • Configuring an ODBC Connections (User, System, File)
Other Powerful Features • English Query • Online Analytical Processing (OLAP)