Question
Over the weekend, a company's transaction database was moved to an upgraded server. All validations performed after the migration indicated that the database was functioning as expected. However, on Monday morning, multiple users reported that the corporate reporting application was not working.
Which of the following are the most likely causes? (Choose two.)
- A. The access permissions for the service account used by the reporting application were not changed. Correct
- B. The new database server has its own reporting system, so the old one is not needed.
- C. The reporting jobs that could not process during the database migration have locked the application.
- D. The reporting application's mapping to the database location was not updated. Correct
- E. The database server is not permitted to fulfill requests from a reporting application.
- F. The reporting application cannot keep up with the new, faster response from the database.
Explanation
When a database moves to a new server, every client application must be pointed at the new location (connection string, DSN or host mapping), and the service account the application uses must be granted the same logins and permissions on the new server. The database itself validated correctly, so a stale connection mapping or missing service-account permissions are the most likely reasons only the reporting application fails. A new server does not refuse reporting clients by design, does not replace the existing reporting tool, and faster responses never break a client; jobs missed during the outage would not lock the whole application.
