Borland StarTeam 2009 - Borland Technical Publications
Borland StarTeam 2009 - Borland Technical Publications Borland StarTeam 2009 - Borland Technical Publications
• Uses the default setting of 600 seconds (10 minutes) between cache cleanups.• Uses the default setting of 95% for the storage threshold, the point at which this drive is consideredfull.• Specify custom values by selecting the Custom option and changing any of the hive settings.6. Click Next, and then enter the Data Source Name, user name, and password in the appropriate textboxes.Note: If you are connecting to SSE installed with StarTeam Server, the initial password for thesysadmin(sa) account was "StarTeam123".7. If you are not sure of the values supplied, click Verify Connection to test the connection.8. Click Finish.This action re-displays the Server Administration tool, which shows your new server configuration as achild of the Local node.Note: In addition to creating the server configuration, StarTeam Server adds information about thenew server configuration to your starteam-server-configs.xml file. For more information about thisfile, see the Administering and Using StarTeam guide.4. By default, all server configurations are set to use the TCP/IP endpoint (port) 49201. However, each serverconfiguration on a given computer must have a unique endpoint so it is recommended that you edit thedefault endpoint.To change the endpoint:1. Select the server configuration.2. Click the Start With Override toolbar button (or select Actions ➤ Start with Override from the mainmenu). The Start with Override dialog box opens.3. Enter the endpoint that you want to use in the TCP/IP Endpoint text box, and click OK.Note: You can also change the location where attachments are stored using this dialog box, but yourarely need to do this.5. Be sure to configure your new server configuration (for information, see the Administering and UsingStarTeam guide) and plan a backup schedule for it.Understanding CollationThe physical storage of character strings in Microsoft SQL Server 2005 and Microsoft SQL Server 2005 Expressdatabases is controlled by collations. A collation specifies the bit patterns that represent each character andthe rules by which characters are sorted and compared.Microsoft SQL Server 2005 supports objects that have different collations being stored in a single database.Separate Microsoft SQL Server 2005 collations can be specified down to the level of columns. Each columnin a table can be assigned different collations.In a computer, characters are represented by different patterns of bits being either ON or OFF. A program thatuses one byte (eight bits) to store each character can represent up to 256 different characters. A program thatuses two bytes (16 bits) can represent up to 65,536 characters.Single-byte code pages are definitions of the characters mapped to each of the 256 bit patterns possible in abyte. Code pages define bit patterns for uppercase and lowercase characters, digits, symbols, and special86 | Using StarTeam with Microsoft SQL Server and SQL Server Express Databases
characters such as !, @, #, or %. Each European language, such as German or Spanish, has its own single-bytecode page. Although the bit patterns used to represent the Latin alphabet characters A through Z are the samefor all the code pages, the bit patterns used to represent accented characters (such as é and á) vary from onecode page to the next. If data is exchanged between computers running different code pages, all characterdata must be converted from the code page of the sending computer to the code page of the receiving computer.If the source data has extended characters that are not defined in the code page of the receiving computer,data is lost. When a database serves clients from many different countries, it is difficult to pick a code pagefor the database that contains all the extended characters required by all the client computers. Also, a lot ofprocessing time is spent doing the constant conversions from one code page to another.Single-byte character sets are also inadequate to store all the characters used by many languages. For example,some Asian languages have thousands of characters, so they must use two bytes per character. Double-bytecharacter sets have been defined for these languages. Still, each of these languages have their own codepage, and there are difficulties in transferring data from a computer running one double-byte code page to acomputer running another.For information about synchronizing collation settings with another Windows locale, see the following Microsoftsite:http://msdn2.microsoft.com/en-us/library/aa176553.aspxHow Is the Default Collation Selected?If you upgrade a default instance of Microsoft SQL Server version 7.0 or Server 2000 to SQL Server 2005, orif you install a default instance of Microsoft SQL Server 2005 that will be the version switched with a defaultinstance of Microsoft SQL Server version 6.5 or 7.0, SQL Server Setup carries forward the same collationused in the existing instance of Microsoft SQL Server version 6.5 or 7.0, including obsolete collations.In all other cases, SQL Server Setup chooses the Windows collation that supports the Windows locale of thecomputer on which the instance of Microsoft SQL Server 2005 is being installed. If the computer is using theUS English locale, the instance’s default collation is Latin1_General_CI_AS.Important: On a Japanese double-byte operating system, where the default collation for the SQL Server2005 installation is not supported by StarTeam, you must use a named instance with one of the followingsupported collations.• Latin1_General_CI_AS• Latin1_General_CI_AI• SQL_Latin1_General_CP1_CI_ASThe multi-instance feature of Microsoft SQL Server 2005 supports the use of multiple instances in differentlocales on the same database server.Using StarTeam with Microsoft SQL Server and SQL Server Express Databases | 87
- Page 35 and 36: Installing StarTeam Server on Linux
- Page 37 and 38: Pre-Installation SetupThis section
- Page 39 and 40: StarDrawBorland provides the sample
- Page 41 and 42: Installing StarTeam ClientsThis cha
- Page 43 and 44: 7. Rename this file starteam-client
- Page 45 and 46: Installing on Other PlatformsTo ins
- Page 47 and 48: Installing and Configuring the Star
- Page 49 and 50: Logging on to the StarTeam Web Serv
- Page 51 and 52: 1. Edit the /apache-tomcat-5.5.27/c
- Page 53 and 54: Installing StarTeamMPX on WindowsTh
- Page 55 and 56: Number of Peak Usersmore than 200Re
- Page 57 and 58: 6. In the Choose Install Folder dia
- Page 59 and 60: 3. Install the Root Cache Agent. Yo
- Page 61 and 62: • The Cache Agent installer insta
- Page 63 and 64: Installing a StarTeamMPX Root or Re
- Page 65 and 66: Installing StarTeam Layout Designer
- Page 67 and 68: Installing StarTeam Workflow Extens
- Page 69 and 70: The default installation folder is
- Page 71 and 72: 7. In the Choose Shortcut Folder di
- Page 73 and 74: • Review the settings and click I
- Page 75 and 76: Understanding the Encoding Differen
- Page 77 and 78: 5. Create an initial hive for the N
- Page 79 and 80: Running SQL Scripts for Microsoft D
- Page 81 and 82: • starteam_sqlserver_get_dbinfo.s
- Page 83 and 84: select * from s011. Verify that at
- Page 85: Important: The SQL Server ODBC Data
- Page 89 and 90: 1. Install Oracle Server. Most cust
- Page 91 and 92: After setting NLS_LANG correctly, O
- Page 93 and 94: Creating and Starting a Server Conf
- Page 95 and 96: Number of UsersBetween 15 and 50Bet
- Page 97 and 98: Run: weekly.• starteam_oracle_cre
- Page 99 and 100: • The Oracle database’s net ser
- Page 101 and 102: Native-II Vault FoldersFor server c
- Page 103 and 104: A new server log file is created ea
- Page 105 and 106: Savings Time) information for Easte
- Page 107 and 108: The data is critical and must be re
- Page 109 and 110: Export backups are cross-platform a
- Page 111 and 112: Oracle 10g has introduced a new fea
- Page 113 and 114: Total MemoryRecommended 10gR2 Setti
- Page 115 and 116: AMM is implemented using Memory_Tar
- Page 117 and 118: Microsoft SQL Server (continued)def
characters such as !, @, #, or %. Each European language, such as German or Spanish, has its own single-bytecode page. Although the bit patterns used to represent the Latin alphabet characters A through Z are the samefor all the code pages, the bit patterns used to represent accented characters (such as é and á) vary from onecode page to the next. If data is exchanged between computers running different code pages, all characterdata must be converted from the code page of the sending computer to the code page of the receiving computer.If the source data has extended characters that are not defined in the code page of the receiving computer,data is lost. When a database serves clients from many different countries, it is difficult to pick a code pagefor the database that contains all the extended characters required by all the client computers. Also, a lot ofprocessing time is spent doing the constant conversions from one code page to another.Single-byte character sets are also inadequate to store all the characters used by many languages. For example,some Asian languages have thousands of characters, so they must use two bytes per character. Double-bytecharacter sets have been defined for these languages. Still, each of these languages have their own codepage, and there are difficulties in transferring data from a computer running one double-byte code page to acomputer running another.For information about synchronizing collation settings with another Windows locale, see the following Microsoftsite:http://msdn2.microsoft.com/en-us/library/aa176553.aspxHow Is the Default Collation Selected?If you upgrade a default instance of Microsoft SQL Server version 7.0 or Server 2000 to SQL Server 2005, orif you install a default instance of Microsoft SQL Server 2005 that will be the version switched with a defaultinstance of Microsoft SQL Server version 6.5 or 7.0, SQL Server Setup carries forward the same collationused in the existing instance of Microsoft SQL Server version 6.5 or 7.0, including obsolete collations.In all other cases, SQL Server Setup chooses the Windows collation that supports the Windows locale of thecomputer on which the instance of Microsoft SQL Server 2005 is being installed. If the computer is using theUS English locale, the instance’s default collation is Latin1_General_CI_AS.Important: On a Japanese double-byte operating system, where the default collation for the SQL Server2005 installation is not supported by <strong>StarTeam</strong>, you must use a named instance with one of the followingsupported collations.• Latin1_General_CI_AS• Latin1_General_CI_AI• SQL_Latin1_General_CP1_CI_ASThe multi-instance feature of Microsoft SQL Server 2005 supports the use of multiple instances in differentlocales on the same database server.Using <strong>StarTeam</strong> with Microsoft SQL Server and SQL Server Express Databases | 87