tailieunhanh - v5

The Real MTCS SQL Server 2008 Exam 70/432 Prep Kit- P155: Congratulations on your journey to become certified in SQL Server 2008. This book will help prepare you for your exam and give you a practical view of working with SQL Server 2008. | Self Test Appendix Appendix 75 D. Add your user to the db_ssisadmin database role Correct Answer and Explanation C. Answer C is correct. The package shown was saved to the File System. Packages must be saved to the MSDB database to use package roles. Incorrect Answers and Explanations A B and D. Answers A and B are incorrect because the Rely on server storage and roles for access control protection level must be used and the package must be saved to the MSDB database to use package roles. Answer D is incorrect because you are already a sysadmin and already have the same permissions as the db_ssisadmin role. 18. Your developers and created and successfully tested a package. You have deployed it to your production server and scheduled the package to run using the SQL Server Agent. However when you look at your SQL Server Agent job history you see errors on the SQL Server Integration Services Package step. The errors indicate that the connection to the database failed inside the package. Which of the following should you check to find the problem select all that apply A. Verify that the SQL Server Agent Service account has access to the remote database B. Make sure that the SQL Server Agent service is running C. Make sure that the package was saved with the Rely on server storage and roles for access control protection level. D. Check the package configuration to ensure it is pointing at the right database Correct Answer and Explanation A and D. Answer A is correct. When packages are run by the SQL Server Agent they by default run using the SQL Server Agent s service account. If they service account does not have access to the databases referenced in the package the package will fail. You could create a proxy for the SQL Server agent to use that does have access to the database. Answer D is correct because the package may be pointing to a development database that the production SQL Server Agent service does not have access to. You should check package s configuration