D

daily build, 414

data development lifecycle (DDLC), 200

Data Dude persona, 202

data generation, 212–216

data generator, building custom, 219–224

data tier

multiserver, installing Team Foundation Server, 35–36

SQLServer 2005

authentication, caution against, 117–118

backing up, 126–131

instance license, 36

Team System, illustrated, 4

work item tracking system storage, 277

data warehouse

recreating, 137, 141

SQL Server Reporting Services

core components, 422–423

operational stores and adapters, 423

relational database (fact tables), 424–425

troubleshooting

need for, 437

with Warehouse Setup Tool (SetupWarehouse), 438–439

database

backup, 125–131

build scripts, deploying to existing, 208–209

recovery model, inherited, 123

restoring, 135–136

SQL Server 2005 installation, 39–40

Team Edition for Database Professionals

creating new, 202–203

importing schema, 203–205

managing schema, 205

database server, tasks scheduled against, 124

David, Jean-Luc (Professional Visual Studio 2005 Team System), 5, 172, 407

DDLC (data development lifecycle), 200

default Allow permissions, 102–103

default.aspx folder, 267

defined process capability level, 156

deleting process templates, 181–182

deleting team project, 451–453

Deming, W. Edwards

Out of the Crisis, 158–160

quality management and, 157–158

/deny option, Permissions command, 113

deploying product, 444

description, work item type, 280

detail field

data warehouse field, 282

Report Builder, 433

Developer Division (DevDiv) product group, 459

Developer role, MSF Agile Process Model, 197

Development folder, 266

development tools

extensibility versus customization, 227–228

TFCS

classification service, 229

described, 6, 228–229

eventing service, 229–230, 240–242

linking service, 229, 230–231, 244–246

registration service, 229, 231

security service, 229, 231, 243–244

subscribing to an event, 231–232

TFSOM

described, 232–233

IAuthorizationService, 236–238

ICommonStructureService, 238–240

IGroupSecurityService, 243–244

ILinking, 244–246

IProcessTemplates, 246–247

IRegistration, 247–250

IServerStatusService, 250–251

services, accessing, 235–236

TeamFoundationServer object, 233–235

development tools

VersionControlServer, 251–252

WorkItemStore, 252–254

dimension, data warehouse field, 282

dimensions

field, Report Builder, 433

SQL Server Reporting Services, 426–427

directory

build, 77

Team Foundation Server, 234

disaster recovery

built-in Windows tools, 123

ease of use, 123

importance, 121–122

plan, 122

SQL Server 2005 Backup and Restore, 123–124

third-party tools, 123

Disaster Recovery Journal online publication, 122

distributed load testing, 406–413

distributed teams

challenges, identifying

branch office infrastructure, 395

described, 394–395

Team Foundation Server over The WAN, 395

Web, deploying team portal on, 396–397

described, 393–394

internationalization, 415–418

tools, setting up

distributed load testing, 406–413

shared repositories, 397

Team Foundation Build, 413–415

Team Foundation Server Proxy, 398–406

Do phase, quality management, 161

document template schema, 268–269

documentation

BRUF projects, 149

improvements and best practices, 450–451

infrastructure, existing, 9

MSF, compiling and creating, 179–181

documents, managing, 380

drop site server, 74

dual-server deployment, Team Foundation Server, 11