Borland StarTeam 2009 - Borland Technical Publications

• starteam_sqlserver_get_dbinfo.sqlRun: automatically by StarTeam Server when appropriate.• starteam_sqlserver_get_dbpath.sqlRun: automatically by StarTeam Server when appropriate.• starteam_sqlserver_run_msde_backup.sqlRun: after you customize this sample script for your specific environment. You can run this script whenneeded.This sample script illustrates how to make a backup copy of a SQL Server Express database. Before youcan run this script, you must customize it for your specific environment. (Be sure to lock or shut downStarTeam Server before backing up its database.)• starteam_sqlserver_update_statistics.sqlRun: only if necessary.This script updates the statistics about the distribution of key values in each index, which SQL Server usesto optimize query processing. You do not need to run this script if you have enabled automatic statistics(using sp_autostats), or if you are regularly rebuilding the indexes (by running thestarteam_sqlserver_dbcc.sql or the starteam_sqlserver_dbcc_reindex.sql scripts).Microsoft SQL Server SecuritySQL Server 2005 uses a standard security model that involves the following entities and concepts:• Securable - Represents a resource or target object that requires securing, such as a database view.• Principal - Represents a user who requests access to a resource.• Permission - Access type that is associated with a securable. Permissions can be granted to or revokedfrom principals. For example, Update is a permission that is associated with a table (securable) named R. If Update on R is granted to a user (principal) named U , then U receives Update access on R.Further, SQL Server 2005 supports the following security principals at different levels:• Windows-level principals - Control access to SQL Server instances for Windows Local Login and WindowsNetwork Domain Login.• SQL Server-level principals - Control access to SQL Server instances for SQL Server Login.• Database-level principals - Control access to database instances for database users.To access a SQL Server instance, use a Windows user name or a SQL Server user name that was previouslycreated in that server instance. After you log on, the user name represents you as your security principal atthe server level.If you try to use a specific database in the server, SQL Server searches the appropriate database for anyprevious user who has been mapped to your user name. If SQL Server locates such a user, the correspondinguser name represents you as your security principal at the server level.Orphaned UsersWhen a database user for a corresponding SQL Server Login is undefined or incorrectly defined, SQL Serverdoes not allow the user to log on to that instance. Such a user is said to be an orphaned user of the databaseon that server instance. A database user can become orphaned if the corresponding SQL Server user nameis dropped. Most likely, a database user becomes orphaned after a database is restored or attached to aUsing StarTeam with Microsoft SQL Server and SQL Server Express Databases | 81