Whilst the MCSE certifies familiarity with Microsoft products, it is not, as its name suggests, an engineering qualification. Use of the title engineer is rife within the certification industry and is not limited to Microsoft (For example: RHCE: Red Hat Certified Engineer). Use of the term "engineer" has led to some consternation amongst associations of professional engineers, and allegations that the use of the MCSE name may even be illegal in some jurisdictions where the term "engineer" is regulated by law.

Many critics hold the MCSE qualification in very low esteem, and cynically refer to MCSE as "Must Consult Someone Experienced", or "Minesweeper Consultant and Solitaire Expert".

These criticisms originate from two studying methods that are not exclusively associated with passing Microsoft examinations. The first is cramming, particularly within a boot camp, where a student intensively learns the subject material days before sitting an exam. This method has allowed many students to pass, who, weeks later, retain little knowledge of the subject material. The second method is brain dumps. Brain dumps have generated a business sector whose goal it is to sell past papers, with answers, to students wishing to learn by rote.

Both of these methods, when employed by students lacking prior vocational experience, have resulted in a devalued qualification. However, it is worth noting, not everyone using these methods is inexperienced and many questions on the tests would be difficult for even the most experienced professional without some understanding of the exams' particular quirks.

Microsoft, realizing that the title was not held in high esteem, has begun a process of making the exams significantly more difficult. Microsoft also started taking legal action against individuals caught divulging the contents of exams, which had led to some candidates knowing but not understanding the answers to the exams they were about to face.

Microsoft has recently released two lower-tiered certifications, the Microsoft Certified Desktop Support Technician (MCDST) and Microsoft Certified Systems Administrator (MCSA). These are aimed at helpdesk staff and administrators of small to medium sized business respectively. Since the introduction of Windows Server 2003, MCSE has been retasked towards those managing networks for medium to large sized business.

"Brain dumps" People have been rampantly using brain dumps to pass the test. Using brain dumps is unethical, nonetheless many have used it to gain their certifications. There are companies that offer 100% pass guarantee.

Below is an excerpt taken from an internet editorial concerning this problem [1]:

"The exponential growth in the number of computer-related certifications coupled with the relative ease of their acquisition has led to their devaluation in the eyes of many people in the technology field. In some cases, exam content is easily found by certification seekers (through less-than-honorable methods such as "brain dump" web sites) allowing them to gain certification without knowing, or even understanding, the concepts being tested. Certifying agencies have responded in various ways. Some certification tests have incorporated hands-on testing, although there is no evidence that this reduces cheating or improves reliability or validity. Many have explored anti-cheating methodologies (e.g., Caveon [1]) or expanded their exam content. Others have simply raised the price of certification, in a bid to reduce exam resits (and increase the profit margin per head). Faced with this difficult problem, many certifying agencies have not made any changes."

The MCSE is currently available for two different products, Windows 2000 (to be phased out by 2005) and Windows Server 2003.

A candidate must also pass a single design exam and an elective exam for a total of seven exams. Some Windows 2000 level exams are considered applicable to the Windows Server 2003 track.

For both tracks, candidates must pass design and elective exams (for Windows 2000, one design and two electives, for Windows 2003, one of each), for a total of seven exams. The topic of these exams include network security, computer network infrastructure, Active Directory, Microsoft Exchange, Microsoft SQL Server, and other topics of both general networking interest as well as specific Microsoft products.

Each exam costs approximately US$125. Exams usually take between 2 and 3 hours to complete and consist of between 50-90 multiple choice, drag and drop and solution building questions. Microsoft has recently announced a return to simulated content within exams and students are also required to perform certain common administrative tasks appropriate for the topic at hand.

Study materials are available in multiple formats including online, books and in Authorized classrooms.

Microsoft Certified System Engineer (MCSE) - A certification program offered by Microsoft.
To become an Microsoft Certified System Engineer (MCSE) you must pass a series of standardized tests at Microsoft-approved testing facilities.
On the positive side, the Microsoft Certified System Engineer (MCSE) certification is designed to give employers an easier way of screening candidates. On the negative side, a candidate with an MCSE and little practical knowledge may unfairly receive consideration over a more qualified non-MCSE. Some Geeks think it's worthy to aspire to be an Microsoft Certified System Engineer (MCSE), but others think it's just a waste of time and money to learn the "Microsoft way."

Microsoft Certified Systems Engineer (MSCE) credential is the premier certification for professionals who analyze the business requirements and design and implement the infrastructure for business solutions based on the Windows* 2000 platform and Microsoft server software. Implementation responsibilities include installing, configuring, and troubleshooting network systems. The Windows 2000 track of the MCSE credential is designed for IT professionals working in the typically complex computing environment of medium to large organizations. An Microsoft Certified System Engineer (MCSE) candidate should have at least one year of experience implementing and administering a network operating system. The Microsoft programs focus on computer software. The exams are administered by Prometric and Virtual University Enterprises, independent testing organizations with locations worldwide.

Candidates for this exam operate in medium to very large computing environments that use Microsoft SQL Server 2000 Enterprise Edition. Candidates have at least one year of experience administering SQL Server. They also have at least one year of experience implementing relational databases in environments that contain:

Heterogeneous databases.

SQL Server security integrated with Windows Authentication. Client/server configurations of 50 to 5,000 or more users. Web configurations that use Microsoft Internet Information Services (IIS) or COM+.
Databases as large as 2 terabytes.
Multiple installations of SQL Server 2000.

Skills Being Measured
This certification exam measures your ability to administer and troubleshoot information systems that incorporate Microsoft SQL Server™ 2000 Enterprise Edition. Before taking the exam, you should be proficient in the job skills listed below.

Developing a Logical Data Model

Define entities. Considerations include entity composition and normalization.

Specify entity attributes.
Specify degree of normalization.

Design entity keys. Considerations include FOREIGN KEY constraints, PRIMARY KEY constraints, and UNIQUE constraints.

Specify attributes that uniquely identify records.
Specify attributes that reference other entities.

Design attribute domain integrity. Considerations include CHECK constraints, data types, and nullability.

Specify scale and precision of allowable values for each attribute.
Allow or prohibit NULL for each attribute.
Specify allowable values for each attribute.

Implementing the Physical Database

Create and alter databases. Considerations include file groups, file placement, growth strategy, and space requirements.

Specify space management parameters. Parameters include autoshrink, growth increment, initial size, and maxsize.
Specify file group and file placement. Considerations include logical and physical file placement.
Specify transaction log placement. Considerations include bulk load operations and performance.

Create and alter database objects. Objects include constraints, indexes, stored procedures, tables, triggers, user-defined functions, and views.

Specify table characteristics. Characteristics include cascading actions, CHECK constraints, clustered, defaults, FILLFACTOR, foreign keys, nonclustered, primary key, and UNIQUE constraints.
Specify schema binding and encryption for stored procedures, triggers, user-defined functions, and views.
Specify recompile settings for stored procedures.
Specify index characteristics. Characteristics include clustered, FILLFACTOR, nonclustered, and uniqueness.

Alter database objects to support replication and partitioned views.

Support merge, snapshot, and transactional replication models.
Design a partitioning strategy.
Design and create constraints and views.
Resolve replication conflicts.


Troubleshoot failed object creation.

Retrieving and Modifying Data

Import and export data. Methods include the bulk copy program, the Bulk Insert task, and Data Transformation Services (DTS).

Manipulate heterogeneous data. Methods include linked servers, OPENQUERY, OPENROWSET, and OPENXML.

Retrieve, filter, group, summarize, and modify data by using Transact-SQL.

Manage result sets by using cursors and Transact-SQL.
Considerations include locking models and appropriate usage.

Extract data in XML format. Considerations include output format and XML schema structure.

Programming Business Logic

Manage data manipulation by using stored procedures, transactions, triggers, user-defined functions, and views.
Implement error handling in stored procedures, transactions, triggers, and user-defined functions.
Pass and return parameters to and from stored procedures and user-defined functions.
Validate data.

Enforce procedural business logic by using stored procedures, transactions, triggers, user-defined functions, and views.

Specify trigger actions.
Design and manage transactions.
Manage control of flow.
Filter data by using stored procedures, triggers, user-defined functions, and views.

Troubleshoot and optimize programming objects. Objects include stored procedures, transactions, triggers, user-defined functions, and views.

Tuning and Optimizing Data Access

Analyze the query execution plan. Considerations include query processor operations and steps.

Capture, analyze, and replay SQL Profiler traces.
Considerations include lock detection, performance tuning, and trace flags.

Create and implement indexing strategies. Considerations include clustered index, covering index, indexed views, nonclustered index, placement, and statistics.

Improve index use by using the Index Tuning Wizard.

Monitor and troubleshoot database activity by using SQL Profiler.

Designing a Database Security Plan

Control data access by using stored procedures, triggers, user-defined functions, and views.

Apply ownership chains.
Use programming logic and objects. Considerations include implementing row-level security and restricting direct access to tables.

Define object-level security including column-level permissions by using GRANT, REVOKE, and DENY.

Create and manage application roles.